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 <[EMAIL PROTECTED]> | 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/
