[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Policy for merging into stabilization was Re: Patch needed for javahl in release 0.34

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-11-29 22:14:27 CET

--On Saturday, November 29, 2003 8:00 AM -0600 Ben Collins-Sussman
<sussman@collab.net> wrote:

> I agree. The point of having the branch exist for a week is so that it
> can "stabilize". Stabilize doesn't mean "avoid all commits no matter
> what." It means, "no new features or large code changes."

How about requiring 3 +1s on a patch before it can be merged into the release
branch *after* the branch has been created? This would allow the "Everyone
agrees it needs to be fixed and it works" to be merged, but not allow anything
that doesn't have explicit confidence to enter the branch. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 29 22:15:19 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.