On Mon, 2006-11-09 at 11:28 -0400, Tres Seaver wrote:
> Philipp von Weitershausen wrote:
> > Jim Fulton wrote:
> >> I agree in principle.  In practice, I'm not sure we have enough
> >> maintainers to get a release out, let alone maintain two previous
> >> release branches. :(   We need more volunteers.
> The marginal effort to do the bugfix correctly (i.e., first on the
> release branch, then forward-porting to any beta branch and the trunk)
> is not that big.  If we can't get our volunteers to do that, then maybe
> we need to quit pretending that Zope3 is or ever will be "production
> ready."  Without such a practice (which Zope2 has had since before
> community checkins), how can we expect anybody to take Zope3 seriously?

I've only ever worked on one open source project where I was not
supposed to backport my fixes to the maintenance release branches and
that is Plone.  For Plone we have someone responsible for back-portting
that stuff in bulk.  It makes his job harder if we manually back-port
fixes as then he has to be more selective with the patches he backports.

Thanks Hanno!

But my point is it is pretty standard behaviour to have to backport
fixes to all actively maintained branches.

- Rocky

Rocky Burt
ServerZen Software -- http://www.serverzen.com
News About The Server (blog) -- http://www.serverzen.net

Attachment: signature.asc
Description: This is a digitally signed message part

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to