What guides or standards do you use for CVS in your team ?
- by PaulHurleyuk
I'm starting to do a small amount of development within my company. I'm intending to use Git for CVS, and I'm interested to see what guidelines or standards people are using around CVS in their groups, similar to coding standards are often written within the group for the group.
I'm assuming there will be things like;
Commit often (at least every day/week/meeting etc)
Release builds are always made from the master branch
Prior to release, a new branch will be created for Testing and tagged as such. only bug fixes from this point onwards. The final release of this will be tagged as such and the bug fixes merged back into the trunk
Each developer will have a public repo
New features should get their own branch
Obviously a lot of this will depend on what cvs you're using and how you've structured it.
Similar Questions;
http://stackoverflow.com/questions/273695/git-branch-naming-best-practices
http://stackoverflow.com/questions/2006265/is-there-an-standard-naming-convention-for-git-tags
