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

Re: question about multi-level trunk/branches/tags structure

From: F.J. Weiland <fj_at_effjay.com>
Date: 2007-04-08 08:01:46 CEST

I've got the same question & just found this brief info exchange on the
topic in the archives.

http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=23867

I'm transitioning over to svn from another tool that works very
differently, so I'm having to adjust a bit.

Given two parallel lines of development, a main line and a new-feature
line, using subversion, what's the "school solution" for marking the
changes in the new-feature line?

In subversion terminology, given a trunk and a branch called new-feature,
how am I supposed to "tag" important builds of the new-feature branch --
make a tags directory under the new-feature branch, or use the top-level
tags directory and be clear about the tagname given?

e.g.

A. using a build-specific tags directory:
/project/trunk
        /tags/maintag1
        /tags/maintag2
        ...
        /branches/old-feature
        /branches/new-feature
        /branches/new-feature/tags/new-featureRC1
        /branches/new-feature/tags/new-featureRC2

or

B. using only the main tags directory:
/project/trunk
        /tags/maintag1
        /tags/maintag2
        /tags/new-featureRC1
        /tags/new-featureRC2
        ...
        /branches/old-feature
        /branches/new-feature

Which is considered the "Right" way to do this with subversion?

Thank you,
fj

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 8 08:02:10 2007

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