I am currently trying to build the next Zope 2.9 and Zope 2.10 releases.
I would like to ship the release with the latest Zope 3.2 and 3.3 *tagged*
releases. At least Zope 2.9 refers (because of a bugfix) to zope.interface
on the 3.2 branch. I definitely won't make 2.X releases with a svn:external
mixture against branches and tags. Are there any objections creating tags
for 3.3.2 and 3.2.3 based on the current code on the 3.3 and 3.2 branches?
I see also problems coming up when using the satellite projects with their
own release schedule within Zope 2. It will be hard to track changes and make a decisions which if of the packages needs to be updated. The Zope 3 meta-egg or how ever we will call it is most important since it has to describe the officially blessed versions of all packages.


Attachment: pgprP3ZWiCMJR.pgp
Description: PGP signature

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to