[Top][All Lists]

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

RE: Commitinfo question

From: Greg A. Woods
Subject: RE: Commitinfo question
Date: Wed, 25 Oct 2000 02:41:35 -0400 (EDT)

[ On Tuesday, October 24, 2000 at 15:18:20 (-0700), Ryan Hennig wrote: ]
> Subject: RE: Commitinfo question
> Perhaps I should clarify my intentions in setting up the system that I
> described.  My team is building a system that enforces the policy that a
> developer should only commit code that has been code reviewed, and is ready
> to be included in the build.  This way the repository contains only
> "blessed" code, and whoever does a cvs update picks up clean code that is
> guaranteed to have been built and tested.

What you're talking about here is what's sometimes called a "two-phase"
commit scheme.  The developer "commits" his code to the revision control
system and then the reviewer "publishes" it into the baseline.

The best freely available tool for implementing this kind of system (and
perhaps one of the better tools all-round for this), is Aegis.  I would
suggest you look at it, even if only for ideas:


You can also do this with BitKeeper, though with slightly different
mechanics.....  <URL:>

                                                        Greg A. Woods

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

reply via email to

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