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

Re: 0.33 == Beta

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-11-12 01:52:12 CET

On Tue, Nov 11, 2003 at 04:43:37PM -0600, kfogel@collab.net wrote:
> We're getting down the wire on 0.33. Issue #1429 will be closed soon;
> #1578 is just waiting on a merge from cmpilato; #1595 has a concrete
> plan and is not a lot of coding; Sander's working hard on #1245
> (sitting right here next to me :-) ). We still have to figure out
> exactly *what* if anything we want to do for #1556, but once we've
> decided, we'll know how to do it now, thanks to Philip.
> In case anyone missed it, the plan is that 0.33 == Beta. So after
> Thursday, we'll finally be out of Alpha.

Euh. It is end of day Tuesday. There are two branches corresponding to
issues 1429 and 1578. Each of these are large, structural changes to the
operation of Subversion, and neither has been merged.

I *really* don't think it is a good idea to merge them a day or two before
release. I believe they need some "soak time" before hitting the public at
large. And especially bad to call that release "beta" after such a short
period of "in-trunk-ness".

IMO, keep 0.33 as an alpha. Do the branch merges *just after* 0.33 is
released. If you can release 0.33 today/tomorrow [because 0.33 won't be
held for these merges], then just fine. Then call 0.34 the beta, after
there has been adequate soak time.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 12 01:54:00 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.