[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: Nick Patavalis <npat_at_efault.net>
Date: 2005-01-12 23:13:39 CET

On 2005-01-12, Ben Collins-Sussman <sussman@collab.net> wrote:
>
> The HACKING file in subversion's source tree describes our own release
> process.
>

While I understand the release management pattern as described in the
svn book, the "Stabilizing and maintaining releases" section in the
HACKING file is a bit confusing. Especially this:

  Minor and major number releases go through a stabilization period
  before release, and remain in maintenance (bugfix) mode after release.
  To start the release process, we create an "A.B.x" branch based on the
  previous release, for example:

     $ 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? Immediately after A.(B-1).C
is tagged, or later-on, after some work has accumulated in the trunk
(or somewhere else). If the latter is true, then why is A.(B-1).C
copied (instead of the trunk), and how do changes accumulated in the
trunk reach into A.B.x? If the former is true, then do developers
commit directly in A.B.x instead of in he trunk? Obviously I'm missing
something very important here, or I'm just being stupid.

If I'm not abusing your time, could you please elaborate a bit on
this?

/npat

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 12 23:16:17 2005

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