Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty of time to test.
This sounds good. Here's another idea, though: In accordance with
"release early and often", how about scheduling the 2.12 release shortly
after the 2.11 one? So the only "new" thing in 2.12 would be the
philikon-aq branch (it would still ship with the same Zope 3 libraries
as 2.11, etc.).
I suspect we want to do something about the eggification story of Zope 2
for Zope 2.12 as well. Figuring out the approach and documenting it
might take some additional time. I don't see that releasing another Zope
2.13 shortly after 2.12 makes a lot of sense.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -