patch tracking

[Diego Novillo]

On Fri, 14 Sep 2001, Joe Buck wrote:

> I realize that GNATS is not ideal for patch-tracking, but it's already
> in place.
> 
> Thoughts?
> 
I second the idea.  We use a similar system internally.  We have
GNATS categories for each major component of the compiler.  Each
category  has a primary and a secondary reviewer.

The system is setup so that primary reviewers are not necessarily
experts, but wish to gain more experience in that area.  If a
patch is too elaborate, the secondary reviewer provides
assistance.

Patches submitted to the internal GNATS database are copied to
the developer mailing list as well, so that anybody can jump in
if they want to contribute.

The patches have these states:

open::Default state for a new patch.
assigned::Patch assigned to a reviewer.
feedback::Patch is awaiting further explanation from submitter.
applied:closed:Patch has been applied. No further work on it is necessary.
rejected:closed:Patch has been rejected by reviewer or withdrawn by submitter.
closed:closed:This patch no longer active; it is resolved or otherwise defunct.


Diego.