DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34088>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34088 ------- Additional Comments From [EMAIL PROTECTED] 2005-06-07 15:59 ------- [EMAIL PROTECTED] wrote: > 5) Upgrading causes headaches. > This is difficult for all software. Some companies/projects just > announce old implementations will not work with the latest release; > those companies tend to disappear. > > My company details how each code change will affect the previous > release, and if so, requires the patch to fix the upgrade process too. > We do require upgrades to every release; each upgrade only handles > the last release; but we release seldom enough (and the upgrades are > free) so all of our customers have upgraded before the next release. > > Lenya is more complicated because of parallel development. Will > everybody need to upgrade 1.2.2 to 1.2.3 to 1.2.4 to be able to > upgrade to 1.4? This could be required if upgrades were easy, but the > 1.2.2 to 1.2.3 upgrade issues will hurt. Lenya1.4 needs upgrade code > for each 1.2 release starting with 1.2.2. There will be milestone > releases where all the upgrade code is discarded. > > Our process loops through each document, and calls the appropriate > upgrade function. The functions only deal with one type of document. > Lenya should have an upgrade process for XSL, XSP, JS, XMAP, IML and > GML, various XCONF, siteree.xml, content XML, Flow Form XML, and more. > Each file should be considered as a data during upgrade. Some is > easy. Modifications outside a publication should be discarded; anyone > who customizes the main program must remember their changes, except > maybe the publication "upgrade XSL" could be applied to the global XSL > (for "login" and "choose publication") XSL if those documents have not > changed much. Creating a framework for this is a chore, but it should > only need to done once. Hopefully Lenya can implement something > similar, and figure out how to make it mandatory for each patch to > keep it current. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
