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

RE: Looking for ideas for a tag/release svn usage model

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Tue, 1 Sep 2009 10:33:40 +0100

Given all of your requirements, I think you do need to use SVN branches,
however - create a branch that is the 'development trunk', let users
commit to that. Then after their changes have been verified, someone
else (eg a build manager) merges the dev trunk to the "release trunk".
This way, developers use their existing model - they just use a
particular directory in SVN, and your verified designs are retrieved
from the guaranteed-ok directory.


The only person who has to worry is the build manager, but he will know
what he's doing with SVN. Once people have gotten used to this approach,
you can start letting them have their own branches, and things will be
SVN heaven.


You can still 'tag' a revision by remembering the revision number, it's
a pity SVN doesn't have support for giving these numbers a
human-readable name (and IIRC someone submitted a patch for just that)
as it would have solved a good deal of similar issues. The canonical
svn approach is to use 'tag' branches for tagging. (personally, I feel
that just clutters the repository up, especially if you release very


You can update your working copy to a particular revision - just specify
the revnum in the update command.




To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-01 11:34:49 CEST

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.