RE: Waiting for a good Control Program

[Chris Albertson <chrisalbertson90278@yahoo.com>]

Dave you are right, If we used CVS we would likely set up at least
two branches.  One for production and one for development.  We
would likely do some kind of beta test followed by a series of
"release candidates" and so on.   But still I think the rule
should apply that one does not check code even into the
development branch without a basic "sanity test" that it at least
loads, runs and doesn't not crash

All the details are still TBD.  I think the rules should depend
of how many people are involved as both users and programmers.
With only oe or two working Mk IVs the testers and users are the
same group, but if we ever get over a dozen sites going software
quality control, version a trouble report tracking will need to
be organized.  First step is just to get away from the one program
to one programmer model.

--- Dave Hamilton <davehamilton@alltel.net> wrote:
> Actually the current code management systems are quite a bit more 
> sophisticated than you indicate.  We use SourceSafe but I know CSV is
> just 
> as capable.  You can have named versions (tested), distribution sets
> and 
> various untested branches off of either of those to share what people
> are 
> currently working on.  Your point about not checking in non tested
> code 
> would be better made that you need someone to move code into the
> current 
> build distribution after several people have tested.
> > 
> ---
> 
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/02
> 


=====
Chris Albertson 
  Home:   310-376-1029  chrisalbertson90278@yahoo.com
  Cell:   310-990-7550
  Office: 310-336-5189  Christopher.J.Albertson@aero.org

__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com