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

Re: Expected post-1.0 release cycle?

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-12-24 02:31:21 CET

--On Tuesday, December 23, 2003 4:11 AM -0800 Greg Stein <gstein@lyra.org>

> On Mon, Dec 22, 2003 at 11:49:00PM -0500, Greg Hudson wrote:
>> On Mon, 2003-12-22 at 22:48, Justin Erenkrantz wrote:
>> > I think the branch should really be 1.x, not 1.0.
> Ick.
>> What would we do, merge the entire trunk to the 1.x branch each time we
>> gear up for a new 1.x? Merge specific new features?
>> Even if we make frequent new 1.x releases and desupport 1.x as soon as
>> we come out with 1.x+1, we can do that while still creating a new branch
>> off the trunk for each 1.x release.
> Agreed.

My concern is that committers will want to add new functionality to a 1.x
release when 1.x+1 release has already been released.

If we decide to close the 1.x branch after 1.x+1 is out, then I think we're
just talking really minor points - it's a matter of how best to use Subversion
itself. FreeBSD's model is not to ever close down any branch; changes still
go into every prior release. I think that'd be a giant nightmare.

I only want one open 1.x branch at a time. I'd do that with one directory,
but it could be cleaner multiple copies (hey copies are cheap). *shrug* --

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