Since this particular bug should be circumventable (new word?) by
using Five 1.3.1, it's not serious enough to warrant a release by
itself, IMO.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts
[Jeff Kowalczyk]
What does the twice-annual release policy say about bugs and/or packaging
errors that are identified and fixed within a very short time of the
official release announcement?
I think the answer you're looking for is that the policy says nothing
about that. Every-6-months
What does the twice-annual release policy say about bugs and/or packaging
errors that are identified and fixed within a very short time of the
official release announcement?
Log message for revision 41228:
Merge r41227 from 2.9 branch:
Update Five to bugfix release 1.3.1.
--On 8. Januar 2006 17:49:01 -0500 Jeff Kowalczyk [EMAIL PROTECTED] wrote:
What does the twice-annual release policy say about bugs and/or packaging
errors that are identified and fixed within a very short time of the
official release announcement?
huh? I don't understand. Bugfixes will be
