Hi!
Tres Seaver wrote:
Philipp von Weitershausen wrote:
Andreas Jung wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk should only be
used for bugfixes *only* until the branch is cut. So no new development
and feature should happen on the trunk until then..Use your own branch
until the trunk is open for new stuff to appear in Zope 2.11.
I think we've had this discussion with Zope 2.9 already... I would
prefer if we could make the branch now.
+1. Our policy says[1]:
At the time the first beta of the new feature release is made, we
create a new branch for that feature release (rooted at the trunk
at the time the first beta is made)
I'll make the branch if no-one else has, via the following command line
(using the later revision from which the actual release tag was cut)::
$ svn cp -r 68385 $ZSVN/Zope/trunk $ZSVN/Zope/branches/2.10
[1] http://www.zope.org/DevHome/Subversion/ZopeDevelopmentProcess
I would vote for a compromise:
The branch should be created as soon as somebody wants to work on new
features.
As long as this is not the case the branch is just an extra burden and
doesn't provide any benefits.
Just my 2 cents.
Cheers,
Yuppie
_______________________________________________
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 )
