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

Re: Release management policy fundamentals

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-01-13 04:40:59 CET

On Jan 12, 2005, at 4:13 PM, Nick Patavalis wrote:
>
> $ svn cp http://svn.collab.net/repos/svn/tags/A.(B-1).C \
> http://svn.collab.net/repos/svn/branches/A.B.x
>
> I don't get this. When is A.B.x created?

Yikes, I think you found a bug in our docs! I agree, that example
makes no sense at all. I just confirmed this with our release manager,
and he concurs that it's nonsense. It seems to imply that we'd soon be
creating our 1.2.x branch by copying the 1.1.2 tag, rather than /trunk!

But that's absurd. All new features are developed on trunk. And we
always copy /trunk to /branches/release-branch. That's how we created
/branches/1.0.x, /branches/1.1.x, and that's how we'll create
/branches/1.2.x soon.

Thanks for finding this, we'll fix.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 13 04:44:13 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.