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

trunk, release branches, and tags?

From: Martin J. Stumpf <mjs_at_jhu.edu>
Date: 2006-01-27 15:55:56 CET

Hello all,

Given that subversion uses repository global revision numbers and the
fact that only unversioned revision properties are modifiable on
previous revisions, why is the setup of trunk, branches, tags really

I have been using a release branch and then tagging for releases. I
merge the current trunk into the release branch , update the package
version number, and then create a tag. I treat the tag as "read only"
(no check-ins). It seems like an unnecessary step given the above. I
have just added a version data structure to each of our libraries and
applications can now simply retrieve the revision number that was put
into the library at build time. (I use svnversion to get that and create
a uniquely named global version data structure for each library).

If I am thinking about this correctly, then if a problem is discovered
at runtime on our applications, and I know which subversion revision a
library was built from, then all I have to do is check out that revision
to look for the problem.

Am I missing something here? Are release branches and tags really
necessary? I do use feature branches of course and realize their value.
It is just the tagging that seems unnecessary.

Thanks for your comments,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 27 16:04:46 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.