[Pipet Devel] Development model proposal

Jean-Marc Valin jean-marc.valin at hermes.usherb.ca
Wed May 24 11:28:32 EDT 2000

> We all run Unixxes, so maybe we could setup a cron\at scheme so that we
> all commit our code dayly, and check it out after all commit are
> finished?

Automatic commits won't work because you always need to do an update before you
can commit a file that needs a merge. And the resulting code is very likely not
to compile.

Now I'm not sure e-mails would be the right solution. The likely outcome is that
it will generate enough trafic that noone will look at it. If you read the
section "What is CVS not?" in the book, you'll see "CVS is not a replacement for
communication" ie, we should not try to automate everything. I suggest commiting
small changes regularly and sending e-mails only when breaking source
compatibility. I think with a little coordination and care, we can avoid most
problems with little pain.


Jean-Marc Valin
Universite de Sherbrooke - Genie Electrique
valj01 at gel.usherb.ca

More information about the Pipet-Devel mailing list