After start using the branch, merge and tag technology provided by CVS, it comes up to me with some concerns - naming convention of those tags.
Since the name for these can be anything designed by the users of CVS, we should make some conventions, so that users can clearly understand the under meanings.
Something I want:
- The names should clearly describe whether it is tag for version or branch.
- The names should describe the version of the tag.
- It should show me the projects it belongs to.
- The tags should only be created by a project leader (it’s for better project management)
References:
A Project in Stanford - http://smb.slac.stanford.edu/research/developments/blu-ice/dcsAdmin/node7.html
An example - http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/doc/CONVENTIONS
No comments
Comments feed for this article
Trackback link
http://blog.planner4u.org/blog/2006/07/30/cvs-naming-conventions-for-tags-and-branches/trackback/