What are the best practices for managing source code?

Question

After the recent “crash” at work, when some errors that were previously fixed were re-introduced, I was asked to document a set of recommendations for using source control (CVS in this case).

What are your best practices for using source control? In particular, how do you manage branching and labeling and how do you guarantee that the current release of products can be fixed while continuing to develop new features? For context, the team size is up to 10 developers in two places.

Answer 1

8 Commandments of Source Control pretty much sums it up.

On the topic of branching and labeling of what we do at work:

Labeling

When an environmental release is ever issued, it is marked with at least the release date. All (related) errors are then set so that the "permitted in release" is this label.

Branching

Created only as needed. The branch is made from a shortcut so that you can make changes to a previously released version (that is, fixing a release error without considering all other bug fixes).

Answer 2

Eric Snick has already put it in his Version Control .

Answer 3

I am not sure that I would put “CVS” and “best practice” in the same sentence. There are many other, better, more modern version control solutions that are well supported by the community.

Answer 4

The basic model. Tofu scale.

Read the following: http://oreilly.com/catalog/practicalperforce/chapter/ch07.pdf

Answer 5

update as often as possible (depending on the growth rate of the project) in this way, fixed files cannot be re-entered. Assign developers to upgrade before launch.

Answer 6

There are various types of workflows , you will need to consider what best suits your team needs.

I also always recommend the SVN Book .

Answer 7

The book Pragmatic Version Control (using Subversion) is a really good place to start. Although its examples are specific to Subversion, it is a good introduction to all important concepts and practices.

Answer 8

We try very, very hard not to fork. If we create an affiliate, this is a team decision and is being carefully studied. Therefore, I suggest that the practice will be "not blown lightly."