Currently it is possible to upgrade (via yum or gui) from an unstable version (4.01 or 4.03) to 4.20, without "stopping" in between.
I feel there should be a mechanism in place to prevent this unless manually overridden. For example, if running a 4.0x version prior to 4.0.4 (4.0.0, 4.0.1,4.0.2,4.0.3), upgrading to 4.2 would most likely result in a broken system, because an intermediate update did not take place and the schema did not get extended. Does it make sense to have an upgrade run "database upgrades" of anything in between automatically and allow the upgrade to happen or does it make more sense to make the user stop at each version along the way one by one? Is there a better way to approach this or is something already underway I didn't see? Tony
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
