From: Tobias Burnus <[EMAIL PROTECTED]> Subject: Re: [Fwd: Bug tracking system for ConTeXt] Date: Wed, 27 Feb 2002 12:23:20 +0100 (CET)
> Hi, > > Marko Schuetz <[EMAIL PROTECTED]> wrote: > > have you considered using Peter Miller's Aegis? Currently it seems > > that many of the ConTeXt users would be capable of rephrasing their > > bug report as a test for desired functionality. So this would open a > > new way to contribute: by writing tests... > Correct me if I'm wrong, but it seems that Aegis is more a CVS replacement > than a bug tracking system. (http://aegis.sourceforge.net/) You are right: it is not a bug tracking system, it's quite different from CVS though. While it does provide a repository, it provides features on top of that: - functionality is specified by the collection of tests in the project - the baseline is sure to pass all the tests - changes aren't merely textual modifications of files, they are collections of files together with tests that witness the change in functionality - by default aegis uses three roles: developer, reviewer and integrator, requiring (again by default) that after a developer finishes development on a change another pair of eyes review the change and in particular verify that sensible tests are provided. Then the third role, the integrator, is the only role allowed to integrate the change into the basline. The whole process and project setup is highly configurable. > While I think a move to a CVS like (or based) system would be great, I > think this independend of bugreports/feature request tracking. I agree... > Additionally in order to make it work, we would require that Hans switches > to such a system > > > >From personal experience I can attest that Aegis is a great tool to > > steer software development... > A revision based system wouldn't be bad, that's true. The problem is that > Hans version needs to be available in this system and frequently be > updated. Otherwise it doesn't make that much a sense. > > Does someone know where the strength of these RCS lay? > - CVS (http://www.cvshome.org/) > - Subversion (http://subversion.tigris.org/) > - arch (http://www.regexps.com/#arch) > - aegis (http://aegis.sourceforge.net/) I used CVS extensively before I started using Aegis. I use Aegis for software development and CVS remains in use for changes that aren't changes in functionality. As far as I know these two are the more mature of the lot. The others I only know from their project announcements. Best regards, Marko
