Re: tags versus branches

Kirk Gramcko wrote:
> Hello,
>
> I am trying to decide how best to structure my repository.
>
>
>
> I understand the purpose of a tag is to effectively label a snapshot of
> the project at a given point in time, and that the purpose of a branch
> is to permit development work to continue outside of the trunk area
> starting at a selected point in time. I also understand that tags and
> branches are essentially equivalent to one another when they are created
> (using “fast copies”).
>
>
>
> However, I do not see why I should bother to create a separate directory
> in the repository for TAGS versus BRANCHES. Why not simply have a TRUNK
> directory for new development work, and a BRANCHES directory for either
> tags or branches? After all the only difference between a tag and a
> branch is whether the code is modified after it is created.
>
>
>
> Can anyone suggest a reason to bother with a third directory called
> TAGS? I appreciate any insights into this that I may have overlooked.

Yes, there is a reason: imagine you have a lot of branches and tags.
Have a look at the repository of the Subversion project:
http://svn.collab.net/repos/svn/branches/
http://svn.collab.net/repos/svn/tags/

by keeping the branches and tags in separate directories, it is not so
crowded. And you also know immediately what is still being worked on and
what is considered stable.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net