chris snow wrote: > If migration from old releases to newer ones was more automated (e.g. > providing db migration scripts, ensuring consistent apis between releases, > etc), it would be more practical to have only one (maybe two) stable release > (i.e. supported). I imagine the main reason for users wanting very old > releases to be supported is because the manual upgrade process is very > laborious.
I have a plan to support in-place database upgrades. Need to find where I did that. > > Shouldn't we make is easy for uses to upgrade to the latest stable release > to make it easier to phase out old releases?
