[cvsnt] Workflow advice saught

[Ian Epperson]

> -----Original Message-----
> From: Drew McLellan [mailto:dru at dreamweaverfever.com] 
> Sent: Tuesday, March 18, 2003 1:16 PM
> To: 'cvsnt at cvsnt.org'
> Subject: Re: [cvsnt] Workflow advice saught
> 
> 
> Ian Epperson wrote:
> > First off, make it policy that all changes are committed 
> before nightly
> > backups run.  Any data loss responsibility falls on the 
> person who was not
> > following policy.  Keep the sandboxes on the local machines 
> and DO NOT back
> > them up.  Use a client like TortoiseCVS to easily show 
> files that need to be
> > committed.
> 
> Already working with TortoiseCVS - it's a nice little tool.
> 
> Unfortunately, I can't force developers to commit changes nightly. I 
> don't want them committing code until it's stable.

I'd recommend re-thinking that stance.  We commit often here.  If we want a
clear definition of code that is an "end product", we tag it.  Note that the
longer you prevent a developer from committing, the greater the likelihood
of having to merge code, as well as greater uncertainty that other
programmers' changes may be incompatible.  For having multiple programmers
making lots of fast changes to a project, rapid commits are essential.

So far, our record for highest version number stands at 1.191 for an events
include file.