In these few weeks, I’m working on the conventions of coding stuff in my new company. One of the issues is CVS
CVS, a tool which helps to keep track on the versions of files, source codes, documents. A company must benefit from CVS a lot, if it really uses the functions efficiently. In fact, it seems not the case in my company.
The use of CVS in my company does not have a long history, many of my colleagues don’t even have the mindset on version control in one or two years before. After introducing CVS, they learnt to keep versions at least in each release. But, they just take CVS as a backup tool, and would commit the whole project, including dummy files, compiled files, and also unchanged files. This must not an efficient use of CVS. That’s also the reason why I would like to set up some conventions on using CVS. Here will collect some information from the web.
http://ximbiot.com/cvs/manual/
http://www.bairov.com/2005/09/28/cvs-naming-convention/
http://www.eclipse.org/articles/Article-CVS-branching/eclipse_branch.html
No comments
Comments feed for this article
Trackback link
http://blog.planner4u.org/blog/2006/07/16/cvs-convention/trackback/