Scott Lawrence wrote: > On Thu, 2009-12-10 at 15:08 -0500, Damian Krzeminski wrote: > >> We probably should start dropping really old patches and really old init >> task soon. As of now you can upgrade sipXconfig DB starting old the way >> back with version 3.0. I think it would be OK to carry over 2-3 release >> worth of patches. That would clean up database directory and shorten >> database.xml significantly. > > I think we need to be careful about that... what does it really cost us > to support upgrade as far back as possible? Isn't this a one-time cost > at the first startup after an upgrade?
DB upgrade until 4.0 recently was just one of the many aspects of the upgrade process. There were many config file changes that had to work properly for upgrade to succeed. I am pretty sure sipXecs was only supporting upgrades from the last released version. The fact that you can upgrade the database schema starting with 3.0 was an oddity and does not really help normal users at all. We do need to start removing those patches pretty soon. We have 120 of them: having an untested code in the mainline does not help anyone. > > Trading off user inconvenience for developer convenience is not usually > a good choice... > > I don't think that I was proposing any trade-offs. But even if I was: it's really a trade off before how well we support users that regularly upgrade and stay 1-2 releases behind the main vs. users who didn't upgrade for couple of years now. Damian _______________________________________________ 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/
