Tagging Conventions

[Brian Beaudet <bb...@efficiencylab.com>]

I haven't placed any source control in my tags section yet but I'm about
to.  I have a web application that I'm about to make some major changes
to.  It hasn't been placed in my repository yet.  I think I'd first like
to import it (per the usual methods) then make a tagged copy somehow
indicating that this tagged version is in a runnable state (or something
like that) then get to work on the code files in the trunk (as usual).

 

So my overall question is what are some of the naming conventions others
working with Subversion use for their tags?  I've never used release
candidate in my day to day conversations with my customers so I'm not
too fond of that one.  Pilot, beta, v1.1?  What's best practice here?

 

Thanks,

 

Brian M. Beaudet

Director, Research & Development

EfficiencyLab, LLC

www.efficiencylab.com

 

Re: Tagging Conventions

[Gary Feldman <g1...@marsdome.com>]

I've found the common ClearCase convention to be useful in the other
environments I've used: tags are all UPPER CASE, branches are always lower
case.  This is even more useful in Subversion, because it has no built-in
knowledge of  branches and tags.

Customers generally don't get to see your tags and branches, so I wouldn't
let that drive your convention.  Nor are the particular choices of words all
that important, so don't sweat it too much.  Just design them to match your
process, specifically to make sure that you have unambiguous numeric
increments, and that different major states get different words.  For things
that actually go to customers, you need a 1-1 mapping with whatever detailed
version scheme you have in your product.

Gary


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org