[Pipet Devel] Development model proposal

Jarl van Katwijk jarl at casema.net
Wed May 24 08:39:18 EDT 2000

> 2, Check in small chunks of code and changes frequently, rather than
> doing a lot of coding on your local machine and then trying to check
> it all in at once. This is also not a universally accepted way of
> doing things. For instance, on the bioperl project the way things work
> is that people work on big sections on their local machine for a long
> time and then try to merge it with the code in cvs. I think this way
> is a pain, and checking in frequently helps us to find bugs in each
> others code before they get too far.

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

More information about the Pipet-Devel mailing list