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

Re: Branching 1.5.x on 31/03

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-03-18 18:04:05 CET

On 3/18/07, Max Bowsher <maxb1@ukf.net> wrote:
> David Anderson wrote:
> > Hey,
> >
> > Following the thread on dev@ and the thread on users@ asking our users
> > what we should do with 1.5, I propose we branch the 1.5.x release
> > branch at the end of this month.
> ...
> > - A few people remarked that getting the features we have now "out
> > there" is also good for merge tracking stabilization, as we will have
> > time to address bugs in these features before we release the merge
> > tracking behemoth, and could therefore focus more on merge tracking
> > for 1.6.
> >
> > Personally speaking, I like the stabilization argument (MT is a big
> > enough code change as it is, let's try to get other code changes out
> > of the way), as well as catering to those who need stuff other than
> > merge tracking as soon as possible.
> Strong +1 to branching 1.5.x in 2 weeks.
> The presence of Cyrus SASL support alone justifies the release from a
> feature POV, IMO, and the arguments regarding stabilization, quoted
> above, feel very very right to me.
> I do not believe inserting an extra release cycle will slow down MT
> development - even if all of the committers who have been working on MT,
> remain focussed on MT, I think there's enough others of us to work on
> the release engineering.

Still the same feelings here!

+1 for 1.5(branching) in 2 weeks.

Next to SASL, there's also WebDAV mirrors...

I think its a good idea to release the cleaned up ra_dav separate from MT.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 18 18:04:21 2007

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.