Re: [boost] 1.35.0 release tag?

From: troy d. straszheim (troy_at_[hidden])
Date: 2008-05-21 03:05:49

>> They got moved to:
>>
>> svn ls https://svn.boost.org/svn/boost/tags/release 
>>
>> Running "svn log" on some CVS tag finds:
>>
>> svn log --stop-on-copy 
>> https://svn.boost.org/svn/boost/tags/release/Boost_1_30_0
>> ------------------------------------------------------------------------
>> r44321 | grafik | 2008-04-12 07:21:24 +0200 (Sat, 12 Apr 2008) | 1 line
>>
>> Cleanup release tags.
>> ------------------------------------------------------------------------
> 
> Huh.  Well, if we're going to collect all release tags into a
> subdirectory called "release," can we also collect all non-release tags
> into a different subdirectory?  Otherwise, because a tag is just a
> directory copy, it looks like we have a tag called "release."  It just
> gets really hard to keep track of what's going on.
> 

FWIW, we use:

    trunk/
    branches/       (development of new features, misc)
    candidates/
      V03-00-02/    (copy trunk to here when it is time to start
                     hammering on an RC)
    release/
      V03-00-01/    (mv the candidate here at release time)

Since things can get modified (despite draconian restrictions
on who can write to the release/ dir), we set an svn property
RELEASE_REVISION containing the revision number:

   svn ps RELEASE_REVISION '66761' .

at release time.   In practice we haven't had much use for 'tags',
since you're almost always thinking in terms of 'branches'.  If you need to keep
notes about certain branches at certain revisions, you can use
properties as above.

</2cents>

-t