-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 3 Jul 2007, at 10:10, Wichert Akkerman wrote:
Now that the utility vs tool work seems to be settling down and we are
running Plone without any monkeypatches I want to get Plone 3.0-rc1
out the door start of next week. For that to happen I am going to need
a new CMF release as well. Are there any showstoppers to prevent that
from happening? If not, Jens, are you able to cut a release this
weekend?
I'll be very happy to do it, I was just waiting for one last thing:
Rob Miller merged the BBQ sprint work into the GenericSetup trunk,
but then there was a discussion that petered ot. This is where it
started:
http://mail.zope.org/pipermail/zope-cmf/2007-June/026123.html
The conclusion I saw was that a few things should be changed from the
current state and it wasn't clear to me whether I can go ahead and
cut a GS 1.5 release and create a GS 1.5 branch at this point.
So my question to the parties involved: Can we go ahead and cut a GS
1.5 release with the current GS trunk?
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFGig1/RAx5nvEhZLIRAoQIAJ9myDX/ZGqAGJekZJoLfLBmMBxK6ACfbvDW
7Xf3D0RlMyusNLLf2Bz1hNc=
=c4+f
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
