Tagging Conventions

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

 
Received on Sat May 8 04:44:46 2004