From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/7055 Path: main.gmane.org!not-for-mail From: Marko Schuetz Newsgroups: gmane.comp.tex.context Subject: Re: [Fwd: Bug tracking system for ConTeXt] Date: Wed, 27 Feb 2002 15:24:36 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <20020227152436I.marko@kinetic.ki.informatik.uni-frankfurt.de> References: <87vgcj5b0m.fsf@inanna.rimspace.net> Reply-To: MarkoSchuetz@web.de NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035397549 16118 80.91.224.250 (23 Oct 2002 18:25:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:25:49 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: daniel@rimspace.net In-Reply-To: <87vgcj5b0m.fsf@inanna.rimspace.net> Xref: main.gmane.org gmane.comp.tex.context:7055 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:7055 From: Daniel Pittman 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 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