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

Re: svn 1.1: All aboard. Train is leaving the station.

From: <kfogel_at_collab.net>
Date: 2004-07-07 02:09:53 CEST

Greg Hudson <ghudson@MIT.EDU> writes:
> On Tue, 2004-07-06 at 15:15, Ben Collins-Sussman wrote:
> > 1. Freeze /trunk. Roll beta-tarballs from /trunk. After 4 weeks
> > of freeze, we release 1.1 and copy /trunk to /branches/1.1.x.
> > 2. Copy /trunk to /branches/1.1.x. Roll beta-tarballs from the 1.1
> > branch. Allow new development to continue on /trunk. Do a
> > release after 4 weeks.
> I'm okay with releasing some beta tarballs from the trunk, but I think
> we should have a branch for at least a week or so before the release.

In HACKING, we say four weeks of stabilization. Not that we can't
change what's in HACKING of course, but I do think it's a good policy
for major and minor releases.

That means option (2). Given how active trunk has been lately, option
(2) seems like a good idea anyway. It'd be a shame to dampen the
amazing amount of activity going on on trunk -- but it'd also be a
mistake to have that kind of change rate on a line intended for
release in the immediate future.

Basically, I'm in favor of the procedure outlined in HACKING.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 7 03:37:24 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.