Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 4 Oct 2004 16:27:43 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: whole cygwin release/ distribution issues Message-ID: <20041004202743.GE1905@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <41617A93 DOT 6070203 AT x-ray DOT at> <19910627726 DOT 20041004184520 AT familiehaase DOT de> <20041004164801 DOT GN30976 AT trixie DOT casa DOT cgf DOT cx> <4161A053 DOT 7040501 AT x-ray DOT at> <20041004192725 DOT GC1905 AT trixie DOT casa DOT cgf DOT cx> <4161AFB3 DOT 7020408 AT x-ray DOT at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4161AFB3.7020408@x-ray.at> User-Agent: Mutt/1.4.1i On Mon, Oct 04, 2004 at 10:16:51PM +0200, Reini Urban wrote: >Ah, I see. You meant something different. Just a bugzilla or mantis >"Know issues" site. A bugtracker. Couldn't ITP's be tracked also >then? > >Hmm, I'll think of it. I'd need shell access to sourceware then. You wouldn't need shell access to use bugzilla. >>We could use bugzilla, I suppose, and let everyone maintain things, but >>the prospect of that has always scared me after our experience with the >>cygwin todo list. I can see carefully setting up categories for bug >>reporting and then seeing "setup not work" in the cygwin DLL category. > >Very good idea. But I didn't setup bugzilla lately. Heard it got >better. We already have bugzilla on sourceware. I even started setting up some cygwin categories a while ago before I started scaring myself by imagining the scenarios of cygwin users actually using bugzilla. I'm sure that there is something frighteningly non-obvious about bugzilla's use which, while we receive no complaints for gcc, eCos, or any other project, would cause brain aneurysms for some cygwin users and would cause an increase in email traffic here. Regardless, it's probably time to consider using a formal method to track problems. The distribution has surely gotten big enough for that. Actually, I think that one of the 3+ developers even volunteered to help maintain bugzilla when I mentioned this on cygwin-developers. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/