> -----Original Message----- > From: Rupa Bholanath Lahiri [mailto:[email protected]] > Sent: Monday, August 31, 2009 4:57 AM > To: [email protected] > Subject: Best practises for Configuration Management before build > > Hi, > > As there are many experts in Configuration Management in this > group I ask of this opinion here - > Before doing a build there may be a practice to check all > working copies if there are any files which are modified but > not checked-in. > So one person may go around checking status of files in each > person's working copy and accordingly check-in files which > are not checked-in. > Is there any other way to ensure that developers have not > inadvertently left out checking-in files which they should > have checked-in? > > Regards, > Rupa After watching the numerous threads appearing, I feel compelled to recommend the best practice of reading what CVS is and what it is not as described in CVS documentation:
http://ximbiot.com/cvs/wiki/CVS--Concurrent%20Versions%20System%20v1.12.12.1:%20Overview For example: CVS is not a substitute for management. CVS is not a substitute for developer communication. CVS is not a configuration management system. The use of "CVS" in these statements is primarily a result of the statements being made in CVS documentation. The statements are true even when the names of many other version control systems are substituted. Much of the prior discussion appears to indicate that CVS is being asked to be something it is not. This does not mean the tool is inadequate. It probably means something else is inadequate. In my opinion, it would be supremely foolish to attempt to examine working copies. The number of broken working copies, or ones that have no relevance whatsoever to the current build on a server I maintain vastly outnumbers those that are relevant to the current build. It is almost guaranteed that the project would be greatly damaged (in many, many ways, not just the build) by attempting to process working copies. I suggest doing a search on "CVS Best Practices" for a great deal of valuable information on this topic. http://lmgtfy.com/?q=cvs+Best+Practices --- Kevin R. Bulgrien Design and Development Engineer This email message is for the sole use of the intended recipient(s) and may contain General Dynamics SATCOM Technologies confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
