-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jung wrote:
--On 14. Juli 2006 16:01:22 -0400 Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andreas Jung wrote:
If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri).
Even sooner would be fine with me. I plan to release a 2.8.8 this weekend with the changes for the ReST fix (I already released a 2.7.9).
Should not be a problem for me..perhaps Monday...
Note that the 2.9 branch depends at the moment on unreleased ZODB changes (for a fix to issue #2016) and that there is a sizable set of changes on the 3.2 branch after 3.2.1, at least some of which might be important for Zope2.
I think we should make another internal ZODB release. The current svn:externals for the ZODB (and other modules) use a revision number instead of a tag. This reminds me of some former discussion whether to use revision numbers or tags...what was the result of this discussion. I am very much in favor of using tag names...revision number tell you nothing...provide at least a reasonable version information...opinions?
+1. I tagged 'ZODB-3.4.4' and 'Zope-3.0.2-Zope-2.8' "releases" yesterday for internal consumption of the Zope 2.8 branch. I don't expect to make actual releases from those tags, but I like having them there. As we move to a more fine-grained package architecture (i.e., egg-based Zope "districbutions"), we are going to have to do more "releases management" of the individual pieces which make up Zope. Keeping the changelog current will be a bit of a chore, but is essential in a packageing-driven maodel (just as with RPM / .deb packaging). 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.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEuNKv+gerLs4ltQ4RAmELAJ4oRjpr7lJU4m+8qzcXv1EL9JwMnwCglwO3 nPLTzxp2s1dtPbTQjuWI6vE= =II/L -----END PGP SIGNATURE-----