Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
cc: "Corinna Vinschen" <cygwin AT cygwin DOT com>
Subject: Re: no more package moratorium?
References: <F224RS8LbyiDFkBfMPA00001d21 AT hotmail DOT com> <007f01c16cde$5016de20$0200a8c0 AT lifelesswks> <20011114124323 DOT C24614 AT cygbert DOT vinschen DOT de>
Organization: Jan at Appel
From: Jan Nieuwenhuizen <janneke AT gnu DOT org>
Date: 15 Nov 2001 12:19:27 +0100
Message-ID: <m3n11oth6o.fsf@appel.lilypond.org>
Lines: 26
User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Robert Collins <robert dot collins at itdomain dot com dot au> writes:

> I think the process for that part should be something like
> 
> sponsor (for new maintainers) or maintainer (2nd package or new
> version
> of existing) places the packages files at a URL.
> They tell someone from <list of maintainers with write access>.
> <someone> uploads to cygwin.com.
> 
> If there is _any_ doubt about the package quality, upload it as
> experimental. Wait 3 weeks, and if there are no bugs reported, then
> edit
> setup.hint to make that new versiom current.
> 
> Thoughts on this?

What about existing packages?  Specifically, it would be grand if
tetex-beta would either get fixed or removed.

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <janneke AT gnu DOT org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/