info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Setting the rules and politics for CVS...


From: Jim.Hyslop
Subject: RE: Setting the rules and politics for CVS...
Date: Wed, 28 Jul 2004 09:03:30 -0400

address@hidden wrote:
> I´m studying CVS for the first time. I know how to use it now, but I
> don´t know how to make or "config" the rules and politics to make a
> group of about 5 programmers working in the repository. I will be the
> project leader...
> 
> Do you know  a doc or some URL, tutorial or URL with that info?
The manual is available at
https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs.html

It will tell you everything you need to know.

> I want to know thing like: When to make a branch? When to make a tag?
The manual will not tell you that, though. Basically, you apply a tag when
you want to take a particular snapshot of your development. It is better to
err on the side of too many tags than too few (within reason, of course - if
you find yourself applying several tags a day then you're probably going
overboard :-)

You create a branch when you have two different streams of development. For
example, KillerApp version 1.0 is in QA, meanwhile you are working on
KillerApp version 1.1. QA reports a problem in 1.0 - you fix the problem on
the 1.0 branch.

When creating a branch, always first apply a non-branch tag so you can
easily find the base of the branch.

Be sparing with your branches - the more branches you have, the more complex
your development will be (e.g. you have a fix that has to be applied to
branch A and to branch B, but not to branch C unless... get the idea?).

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.com/experts)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]