From: David Abrahams (dave_at_[hidden])
Date: 2007-08-23 12:57:12
on Thu Aug 23 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
> David Abrahams wrote:
>> on Thu Aug 23 2007, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
>>
>>> Wouldn't generally accepted SVN setup be:
>>>
>>> svd/boost
>>> /trunk (same as current trunk)
>>> /tags
>>> RC_1_35_1... (snapshot when tarball is created)
>>> /branches
>>> RC_1_35 (next release in being updated)
>>> joe_shmoes_library_development
>>> ....
>>
>> Yes, that would be usual, and it's roughly what I was going to suggest
>> (the tag RC_1_35_1 should be something like 1_35_1a1, because we may
>> end up releasing multiple release candidates for a given Boost
>> version). Is there a good reason not to follow it?
>
> This is why I asked for a rationale ;-) The two reasons Beman gave (one
> of which I guessed):
>
> * To make the permissions easier to manage. (my words)
> * Focal point for casual browsers to find release related trees.
> (Beman's words)
svn/boost/
trunk/
tags/
...
release/
1_34_1
1_35_0
...
branches/
release/
1_35_0
...
libraries/
python/
serialization/
?
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com