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

Re: RFC: Process for 1.x.0 releases

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-19 04:38:27 CEST

On Fri, 2004-07-16 at 13:02, Greg Hudson wrote:

> So, I'd suggest, for a .0 release:
> * Weeks 1-3: minor bugfixes can go in, following the same criteria
> as we'd use for a patch release (with the API rules relaxed
> because there's no release to maintain API compatibility with).
> We put out a second release candidate at the end of week 3 if we
> made any changes.
> * Week 4: only a critical bugfix can go in, and we put out another
> release candidate and restart week 4 if we do that. Other fixes
> are delayed until 1.x.1.
> * If a showstopper bug forces us to make a significant change, we
> restart the four-week soak period wherever we are. If we can't
> agree informally on whether a fix requires restarting the soak
> period, we vote.

I am *so* +1 on this. If we come to a consensus, I nominate ghudson to
document this in HACKING. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 19 04:40:00 2004

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.