From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Cc: <burnus@gmx.de>, <ntg-context@ntg.nl>
Subject: Re: [Fwd: Bug tracking system for ConTeXt]
Date: Wed, 27 Feb 2002 12:23:20 +0100 (CET) [thread overview]
Message-ID: <Pine.BSF.4.30.0202271213350.74051-100000@warp.physik.fu-berlin.de> (raw)
In-Reply-To: <20020227013324L.marko@kinetic.ki.informatik.uni-frankfurt.de>
Hi,
Marko Schuetz <MarkoSchuetz@web.de> 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/)
While I think a move to a CVS like (or based) system would be great, I
think this independend of bugreports/feature request tracking.
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/)
With warm regards,
Tobias
next prev parent reply other threads:[~2002-02-27 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 12:50 Tobias Burnus
2002-02-27 0:33 ` Marko Schuetz
2002-02-27 11:23 ` Tobias Burnus [this message]
2002-02-27 13:07 ` Daniel Pittman
2002-02-27 14:24 ` Marko Schuetz
2002-02-27 20:46 ` Hans Hagen
2002-02-28 10:57 ` Berend de Boer
2002-02-28 12:28 ` Daniel Pittman
2002-02-28 16:48 ` Hans Hagen
2002-02-27 14:24 ` Marko Schuetz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.4.30.0202271213350.74051-100000@warp.physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--cc=burnus@gmx.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).