Venugopalan V.
Год: 2005
Язык: Английский
Формат: CHM / RAR
Формат файла: RAR
This article outlines some of the best practices that can be adopted when Concurrent Versions System is used as the configuration management tool in your software project.
Concurrent Versions System (CVS) is an Open Source configuration management tool that is now being looked at seriously by many commercial organizations as a viable alternative to other commercial Software configuration management tools.
This spotlight on CVS has led to the inevitable question of best practices for deploying CVS as the backbone SCM tool for large software development projects. Having answered this question many times verbally as a bunch of "gotchas" on CVS, it was time to put down on paper some of the best practices that will work well for CVS based projects.
This paper assumes that the reader is familiar with the fundamentals of software version control. Including features like branching, merging, tagging (labelling) etc., offered by modern version control tools such as CVS
Further, This paper is not an introduction to CVS and its usage. There are excellent articles available on the net for the same. This paper assumes that the reader is familiar with CVS commands and is looking at deploying CVS in his or her organization.