Fog Creek Software
Discussion Board

VSS or CVS best practices


I am looking for source control best practices. Any practical advice/feedback/link  is highly appreciated.


Tuesday, February 11, 2003

Help is just a google search away...

There are tons of pages on this.

Andrew Hurst
Tuesday, February 11, 2003

1)  Organize changes into logical changesets.  The repository should always build, and should always contain maximally self-consistent code.

2)  If you need to check in something half-finished, do it on a branch.

3)  Manage branches with the "flying fish" technique.  Anything more involved is an invitation to disaster in CVS.

4) Use

5)  Use viewCVS

6)  google for  "Top Ten CVS Tips".  Follow that advice.

7)  google for the  "CVS Bubbles Faq-o-matic"

8)  google for "CVS Branch and Tag Primer."

9)  google for "Open Source development with CVS."

Tuesday, February 11, 2003

10. Buy a copy of the book "Open Source Development with CVS", by Karl Fogel and Moshe Bar.
11. Create a repository that's just used for "trying things out", so you can get an idea of what works well and doesn't work well.
12. Find a commercial or free visual merge tool that you're comfort6able with. CVS doesn't come with one, and when you inevitably need to fix a conflict or manage a complicated merge, you'll need one.
13. Don't use the RCS $log feature in your files. The string of checkin comments at the head of the file is less helpful than you'd think.
14. Always, always put in a comment **at the site of the change** when you fix a bug. Makes merging bug fixes back to the main branch easier.


Mark Bessey
Wednesday, February 12, 2003

Be thankful you didn't choose clearcase.

Friday, February 14, 2003

*  Recent Topics

*  Fog Creek Home