Repository Best Practice

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Posts: 5
Joined: Fri Mar 17, 2006 9:24 am

Repository Best Practice

Post by phenderson » Tue May 23, 2006 11:53 am


We're looking to setup 3 distinct folders for each version of our software: development, testing and production. I'm fairly new at source code control and looking for some pointers on the best way to implement this structure. Thanks!

Posts: 346
Joined: Mon Dec 15, 2003 1:52 pm
Location: SourceGear

Post by ericsink » Tue May 23, 2006 6:29 pm

This is usually done with branches. Suppose you start with 'dev' as the main tree in which development happens. Make 'test' a branch of 'dev'. Make 'prod' a branch of 'test'. When you want to promote code, merge the changes from dev to test or from test to prod.

Disclaimer: I'm writing this sort of off-the-cuff, so lots of details are missing and some details may even be wrong. :( I've never done the dev-test-prod style of development, and SourceGear doesn't work that way internally, so I can't speak from experience. See chapter 7 of my Source Control HOWTO for some additional remarks:
Eric Sink
Software Craftsman