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

Re: Proposal: feature freeze (Beta) while stabilizing 1.0.

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-10-04 01:53:02 CEST

kfogel@collab.net wrote:

> I'm reposting this question because maybe not everyone is reading the
> thread 'Re: 0.32, the "1.0" milestone, and the 1.0 release.'
> The proposal:
> After the 0.32 release, let's have a feature freeze and concentrate on
> bugfixing until the 1.0 release. This period of bugfixing will be our
> Beta; there may or may not be interim milestones during it, depending
> on what we find.
> This proposal might be controversial, if there are developers who have
> new features that they're eager to commit, and who don't feel the 1.0
> stabilization process should have such overriding priority... But my
> sense is that most developers want to see 1.0 come out, and understand
> the need for a stabilization period. If that's the case, then we
> don't need to have a separate stabilization branch (with the
> cross-merging overhead that that implies). We can just use the trunk
> as our stabilization branch, and avoid the distraction of watching
> other branches to see what changes need to be ported.
> For/against?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 4 01:53:44 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.