On Sun, Jun 18, 2006 at 02:29:14PM -0400, Christian Theune wrote: > Philipp von Weitershausen wrote: > >Andreas Jung wrote: > >>My recommendation: > >> > >>1 yr deprecation period as it is now > >>1 yr + X maintenance period for older branches. > > > >+1 > > > >Note that this should also extend to the Zope 3 releases. Zope 3.2 is > >part of Zope 2.9 and will hence be used for quite some time. Yet, > >bugfixes aren't even backported to the Zope 3.2 branch anymore... > > > > Is there any chance we can create an overview page that reflects the > status of what changes need to be ported where and what the status of > that branch is? Maybe some kind of matrixy-thingy?
+1, I'd like some way to easily know when a release is no longer maintained. i.e., what's the X in the above formula. as others have observed, bugfixing is easier when you have fewer branches to patch and test... -- Paul Winkler http://www.slinkp.com _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
