Subject: Re: CVS ticket management system
To: NetBSD User's Discussion List <netbsd-users@NetBSD.ORG>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 11/30/2004 18:29:41
[ On Tuesday, November 30, 2004 at 15:27:56 (+0100), Ignatios Souvatzis wrote: ]
> Subject: Re: CVS ticket management system
> On Tue, Nov 30, 2004 at 03:26:01PM +0100, Florian Stoehr wrote:
> > /pkgsrc/databases/gnats ?
> No... that's used for the bug database.
GNATS can work very well (almost) all by itself as an interface and
tracking database for a CVS change management system.
The only trick is in the integration, or rather the automation of
integration. One way it can be done is to post-process the CVS log
messages with a loginfo script to detect commit messages that match a
specified format and which include a PR# and then cause the PR to be put
in"feedback" mode and thus cause the PR submitter and/or responsible
party to be notified that there's a change to be tested. Those commit
messages can be forced to be in the correct specified format too of
Other control features can be implemented as well. E.g. CVS commits can
be blocked (perhaps only on a release branch) unless they reference a
valid, open, PR with some specified state(s), contents, etc. in some
category that might be related to the module, directory, or file, being
worked on, etc.
For Perl hackers the gnatsperl collection of APIs might help with this
integration process: http://sourceforge.net/projects/gnatsperl/
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <email@example.com>
Planix, Inc. <firstname.lastname@example.org> Secrets of the Weird <email@example.com>