Tobias, From: Tobias Burnus <[EMAIL PROTECTED]> Subject: [Fwd: Bug tracking system for ConTeXt] Date: Tue, 26 Feb 2002 13:50:45 +0100
[..] > I installed a bug tracking system (Bugzilla) for ConTeXt and PPCHTeX on > http://bugzilla.physik.fu-berlin.de:8080/context/ > > This location may move in the future (for instance to Hans server), all > data is saved in a separate database (besides "our" bugzilla at > http://bugzilla.physik.fu-berlin.de:8080/bugzilla/) and daily backuped. > The server is presently a Debian Woody Athlon 800 MHz with (only) 128 MB > Ram. > > Hans asked me to stress that he wants to spend more time on coding than > on managing bug reports: > > now, we need to establish a strategy, like, only serious bugs are reported, > > otherwise we end up in spending our lives doing admin work; also, with > > regards to bugs in manuals, i favor 'collected bugs', not one entry per > > type -) 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... >From personal experience I can attest that Aegis is a great tool to steer software development... By default(!) - changes are accompanied by tests - these tests need to fail on the current version and succeed on the changed version - the changes are part of the source code of the project - a change is only added to the baseline if it passes all its tests - the result is that the baseline will always satisfy all its tests Eine sch�ne Zeit Marko Sch�tz
