[Zope3-dev] Zope X3.1? Ane rough feeling for release date?
jim at zope.com
Wed Jan 12 10:15:14 EST 2005
Martijn Faassen wrote:
> Jim Fulton wrote:
>> I suggest the following compromise.
>> I suggest we shoot for time-based releases. Based on some frequency
>> of releases, we'll right down a schedule and, if there is a volunteer to
>> manage a release, then we'll make the release based on whatever is ready
>> at the time. Otherwise, we'll wait until the next release for which
>> there is a manager.
>> What frequency should we shoot for?
> A 3 to 4 month cycle between releases, with a possibility of more
> frequent bugfix releases.
I was talking about feature releases.
> This release cycle is probably too fast for
> the long term, but it can slow down. It's probably a bit too slow for
> the near time given the need for open-source attention, but it doesn't
> seem realistic to go faster.
OK. Then let's try every 3 months.
Stephan raised an important issue to me on IRC. It's a burden
to a thin set of volunteers to support mutiple releases.
I suggest we support the current release and the trunk.
I also suggest that when we make a new feature release, we
automatically make a final bug fix release on the previous feature
release if there are any unreleased bug fixes.
Of course, we can make fixes to older releases or more frequent bug
fix releases by exception.
>> If there was a volunteer, I think we could begin a release nowish.
> I'm not volunteering right now, as I have a hard time enough getting a
> Five release out of the door. :) Perhaps writing a post specificially
> asking for volunteers and what would be needed from them, will get us
OK. Stephan, do we have any documentation for releasers?
Perhaps we can create a wiki page with this documentation.
Jim Fulton mailto:jim at zope.com Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
More information about the Zope3-dev