I have been pretty much done the opposite. There were big changes when they went from 1.4 to 1.5 due to the introduction of Vars. I am newer to gliders and have always used Mike Shellim's templates (shout out to Mike). Still, when I updated the radio into the 1.5 realm I waited until Mike came up with new, "Var improved" templates and then I updated. Here, there is no update path, so I went through and wrote down all my point values and started setting everything up. It wasn't trivial, but it wasn't a major deal. Of course, I only have a few gliders
Anyway, I update when one is available as I don't want to get too far behind.
The one feature I am still asking for is an auto-updater for models. Models are only updated when you actually open them and at one point there was a 1.4 -> 1.5 conversion problem if your 1.4 was less than some value. Given that models are not updated until selected, you could easily have been keeping up to date with updates, but not opened some of your models. This would then lead to failures when you finally opened them. They argue this won't happen again, but I have been a software engineer for 40 years and I can tell you that just ain't true; if it happened once, it can happen again.
If it were me writing the software, Suite would first make a version labeled backup of all models, and then update all of them. Further, each model would have a flag indicating whether or not that model had been opened since it has been updated, so that it could provide a warning dialog informing the user that the model has been updated and to check all functionality before use.
But that's just me.
