[Top][All Lists]

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

RE: Control tagging of labels Test, QA and Production?

From: Jim.Hyslop
Subject: RE: Control tagging of labels Test, QA and Production?
Date: Mon, 19 Jan 2004 11:57:19 -0500

Andy Jones [mailto:address@hidden wrote:
> Allow me to suggest a simpler alternative.
> Developers do not book code into CVS until it is ready to be 
> promoted to QA.
Pardon me for being blunt, but this is a Really Bad Idea. This encourages
people to leave code out of the repository for weeks or even months on end.
There are many nasty side effects to this practise, including the risk of
losing code if your hard drive fails, and increasing the difficulty and
amount of time it takes to integrate code once the code is ready to be
checked in.

CVS works best when you check in frequently, and update your code from the
repository frequently. By frequently, I mean at least once a day.

> Presumably you would not want code included 
> in the automatic build unless the developers had completed 
> it, so your "test" tag works fine as it is.
There's a difference between completing code, and having the code ready to
be reviewed by QA. It also depends on the purpose of your daily build - our
daily build, for example, always uses the head of the trunk, and is
primarily used as a sanity check to make sure nobody broke the build.

Jim Hyslop 
Senior Software Designer 
Leitch Technology International Inc. (<>) 
Columnist, C/C++ Users Journal (<>) 

reply via email to

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