[Zope3-dev] Re: 3.3.1 release planning
On Sep 12, 2006, at 11:56 AM, Martijn Faassen wrote: Hi there, I understand that the 3.3.0 release is coming out next week. Hopefully, that depends depends on how the release candidate goes. As the 3.3.1 release manager volunteer, Yay! I ask everybody to do the following: If you find a bug in Zope 3, please try fixing it in Zope 3.3 branch first, and then forward port it to trunk. The goal here to make sure we fix bugs in 3.3 after the release. We're planning the release for Zope 3.3.1 release for the first week of october, unless something urgent comes up that necessitates a bugfix release before then. Cool. as Christian pointed out, please defer non critical bug fixes until after the final release. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: 3.3.1 release planning
Martijn Faassen wrote: Hi there, I understand that the 3.3.0 release is coming out next week. As the 3.3.1 release manager volunteer, I ask everybody to do the following: If you find a bug in Zope 3, please try fixing it in Zope 3.3 branch first, No, please fix it in Zope 3.2 first. As far as I understand it, this is the rule now. Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: 3.3.1 release planning
Hi, I had an interesting comment from Chris McDonough on a variation how to handle the RC. Instead of blocking changes to the maintenance branch, we could create a temporary RC branch that only the release manager allows checkins to. In this scenario, the maintenance branch stays open for non-critical bugfixes without penalties to other developers. Christian Jim Fulton wrote: On Sep 12, 2006, at 11:56 AM, Martijn Faassen wrote: Hi there, I understand that the 3.3.0 release is coming out next week. Hopefully, that depends depends on how the release candidate goes. As the 3.3.1 release manager volunteer, Yay! I ask everybody to do the following: If you find a bug in Zope 3, please try fixing it in Zope 3.3 branch first, and then forward port it to trunk. The goal here to make sure we fix bugs in 3.3 after the release. We're planning the release for Zope 3.3.1 release for the first week of october, unless something urgent comes up that necessitates a bugfix release before then. Cool. as Christian pointed out, please defer non critical bug fixes until after the final release. -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: 3.3.1 release planning
Martijn Faassen wrote: Philipp von Weitershausen wrote: Martijn Faassen wrote: Hi there, I understand that the 3.3.0 release is coming out next week. As the 3.3.1 release manager volunteer, I ask everybody to do the following: If you find a bug in Zope 3, please try fixing it in Zope 3.3 branch first, No, please fix it in Zope 3.2 first. As far as I understand it, this is the rule now. Good point, I was mixing it up in my mind. Who is the Zope 3.2.x release manager? Me :) ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
