-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEfHXq+gerLs4ltQ4RAq9OAJ45hEfu28lNVpDLundQ3ZEYsJOHqQCgtlQl HApH5B7/uYw383oJOvoMhU4= =JNqN -----END PGP SIGNATURE-----