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

Re: 0.32, the "1.0" milestone, and the 1.0 release.

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-10-03 08:00:04 CEST

On Fri, 2003-10-03 at 00:50, kfogel@collab.net wrote:
> As for 0.32, Beta, and 1.0: The plan is that once 0.32 is complete, we
> are officially "in Beta". At that point, we will make a release
> branch (called "stabilize-1.0" or something), which will be for
> bugfixes only. There will be cross-pollination between trunk and the
> 1.0 stabilization branch, but risky new features will stay confined to
> trunk. When the branch is ready, we release 1.0, and have a party.

Is it really a good idea to branch at beta? Do we really want to try to
be stabilizing for 1.0 at the same time as we're adding features to the
trunk? It seems wiser to just declare a tight feature freeze and have
our whole community behind the same trunk.

I'd say the appropriate time to branch is when we want to prepare for a
1.0.1 release.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 3 08:05:34 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.