If only there were a way...

[Kerbart]

Every time an update comes out I see many asking the question will mod x work in version y? Well, do I have good news for you!

1) Make a fresh copy of your clean install (usually Steam) of KSP. You do have a clean install you won't touch otherwise, right? Right?

2) Install the mod that you're curious about

3) Test whatever functionality of the mod you're interested in

4) Profit!

This will save you of all the agony of having to wait for an answer. You're welcome!

[VoidSquid]

Doing the obvious, but it still seams, many people aren't following these basics.

[Kerbart]

21 minutes ago, VoidSquid said:

Doing the obvious, but it still seams, many people aren't following these basics.

Which for a game so deeply grounded in science is a bit ironic. I've yelled at accountants for not experimenting enough (“What happens if I feed a negative number of periods into an NPV funcion?” — “Why don't you try it out?”) but Rocket Science seems to be founded on “there's only one way to find out.”

[FleshJeb]

Option B: Don’t update KSP.

Don’t let fear of missing out run your life. There’s very little you can do in current versions that you couldn’t do in a modded version 0.25.

The rule of thumb when Squad’s QA was worse was to wait 6 months before updating. Now I’d give it at least 1.

[Kerbart]

Just now, FleshJeb said:

Option B: Don’t update KSP.

Don’t let fear of missing out run your life. There’s very little you can do in current versions that you couldn’t do in a modded version 0.25.

The rule of thumb when Squad’s QA was worse was to wait 6 months before updating. Now I’d give it at least 1.

This is true as well! I tend to rely little on mods — partially for the QA reasons you point out, and the understandable lack of appetite from the mod community to go out and rush the updates out. So I do welcome a lot of the new functionality (either oooooh shiny or now I can get rid of mod x) but if you have a lot of mods then (a) there's not that much new in an update and (b) things are likely to break. In that case the old rule still applies: "wait for the .1 update"