[Top][All Lists]

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

Re: Non-sticky updates to a baseline tag

From: Greg A. Woods
Subject: Re: Non-sticky updates to a baseline tag
Date: Wed, 23 May 2001 14:23:29 -0400 (EDT)

[ On Wednesday, May 23, 2001 at 08:06:24 (-0700), Mark wrote: ]
> Subject: Non-sticky updates to a baseline tag
> I have experienced the developers can be reluctant to update their
> work space regularly. They don't want to pull bad code into their
> workspace to add trouble to their workday.

That would suggest that there's an issue in your development process
that needs urgent attention.  Most successfull development groups have
found that it's really really really bad to ever allow bad code to get
committed to a shared repository in the first place.  This rule of thumb
should probably be applied twice as hard for concurrent development
under CVS!

> Here's what I am looking to do to help encourage regular updates.
> Have an automated build/baseline done early every morning, say 6 or
> 7 AM. Then, if the build is successful, send out an email to
> developers with the tag.

Why not just use peer pressure tactics to "encourage" developers to beat
upon each other whenever one of them checks in broken code?

Otherwise you might find it better to move to a true baseline system
such as Aegis.

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

reply via email to

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