Possibly off topic. Take a look at
http://www.enteract.com/~bradapp/acme/plop98/scm-pats-intro.html, you might get
some ideas.
Noel
[EMAIL PROTECTED] on 2000.02.18 21:43:32
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Multiple developers and code integration
The company I now work for, and the previous company as well, had teams
of developers, 10 or more working on the software projects. Both
companies run the version control system under the restriction that the
repository be the best version of our stuff.
That means that each developer does integration testing (using a small
test suite) every time they check. When one developer is in the process
of doing this integration testing, it's important to make sure that
noone else checks in under them, or else their integration testing would
have missed the other person's code.
We invented a concept (not really original, but was new to most of us at
the time) of a 'checkin hat'. Originally, a toy hat was handed from
person to person, and nobody was allowed to checkin unless they had the
hat. Eventually, someone this to the cvs code, so that the commit would
fail unless you were to top entry on a list. This added a new command
to cvs, called 'hat'.
You would get on the hat list with 'cvs hat -a <message>', and then when
it was your turn, you would grab the hat with 'cvs hat -g'. Then you
would check in, and 'cvs hat -f' to free the hat. This also sent email
to the next person on the hat list informing them that the hat was now
free for them to grab. 'cvs hat -l' showed all the people on the list
with their comments, and a counter of how long they've been waiting, or
how long the hat has been available to them. If nobody had the hat,
only the first person on the hat list could grab it for the first half
hour. If they didn't grab it, then the next person could grab it.
There were also commands to jump ahead of others in the list and drop
back behind others.
The reason I've gone through this long winded description, is to see if
anyone else has run into this kind of problem, and how they have worked
around it. Does everyone create a cvs hat?
If there aren't any other ideas, how does one go about getting new
features into the cvs distribution? I can make the changes, but who do
I submit them to, and who reviews them, etc?
Mike
