ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marko Schuetz <MarkoSchuetz@web.de>
Cc: ntg-context@ntg.nl
Subject: Re: [Fwd: Bug tracking system for ConTeXt]
Date: Wed, 27 Feb 2002 15:24:36 +0100	[thread overview]
Message-ID: <20020227152436I.marko@kinetic.ki.informatik.uni-frankfurt.de> (raw)
In-Reply-To: <87vgcj5b0m.fsf@inanna.rimspace.net>

From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: [Fwd: Bug tracking system for ConTeXt]
Date: Thu, 28 Feb 2002 00:07:05 +1100

> On Wed, 27 Feb 2002, Tobias Burnus wrote:
> > Marko Schuetz <MarkoSchuetz@web.de> wrote:
> 

[..]
> > - aegis (http://aegis.sourceforge.net/)
> 
> Unless I am very much mistaken this is a development process tool that
> works with your choice of revision control system and imposes additional
> process on it.

I'd say it _supports_ additional process, since this is
configurable. You could e.g. set your project's default to not require
tests, give all the people on the project all the roles so that
everyone may develop, review and integrate even their own work etc. In
essence you can disable or customize the additional process that aegis
offers.

> Last I checked it talked about RCS, CVS and SCCS, but may support more.

RCS or fhist are enough. Aegis' history management is configurable:
you configure which command is used to obtain a particular version of
a file, or to add a new "top-most" revision etc.

> This may be a solution to problems of greater scope than revision
> control, which may actually be the problem you are trying to address
> here, but it's not, in and of itself, a revision control system.
> 
> It also implies a lot more formal process than most open source
> development efforts use which, if you are trying to make the development
> of ConTeXt, would most likely impede your aim.

Hmm? Did you leave out some word here? I do not get what exact aim you
mean, and how it would impede this aim.

Cheers,
Marko


  reply	other threads:[~2002-02-27 14:24 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
2002-02-27 13:07     ` Daniel Pittman
2002-02-27 14:24       ` Marko Schuetz [this message]
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=20020227152436I.marko@kinetic.ki.informatik.uni-frankfurt.de \
    --to=markoschuetz@web.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).