X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,EXECUTABLE_URI,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_CG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <cmfq66p4d2s88u1foj5s7d13ucg2oda29i@4ax.com>
References: <4C6C1B01 DOT 4020808 AT blunn DOT org>	<20100818182641 DOT GB22698 AT ednor DOT casa DOT cgf DOT cx>	<4C6C4372 DOT 2070701 AT blunn DOT org>	<20100818205009 DOT GK11340 AT calimero DOT vinschen DOT de>	<4C6D17E0 DOT 5010506 AT blunn DOT org>	<8cdq66dd6mang9d5oseab1v7l20io5epmi AT 4ax DOT com>	<20100819141948 DOT GB19001 AT calimero DOT vinschen DOT de>	<cmfq66p4d2s88u1foj5s7d13ucg2oda29i AT 4ax DOT com>
Date: Fri, 20 Aug 2010 19:47:33 +0200
Message-ID: <AANLkTikdO70873x2vDKubxb1LtkzHubbJ4qvsoz-Ox=E@mail.gmail.com>
Subject: Re: Bug tracker
From: Reini Urban <rurban AT x-ray DOT at>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

2010/8/19 Andrew Schulman:
>> The question is if the maintainers really want that, and cgf and I are
>> just 2 out of ~60 maintainers, maintaining over 1400 packages. =A0From
>> these ~60 maintainers we have quite a few who either don't reply to any
>> mail about their package, or who only reply after some nudging.
>
> Agreed, but OTOH I'd guess that half of all of the bugs reported on this
> list are for just two packages: cygwin and setup.exe. =A0If the maintaine=
rs
> of those two packages think a bug tracker would be useful, we should make
> one. =A0If they don't, it's probably not worth bothering.

setup already has a tracker, using the official sourceware bugzilla.
  http://www.sourceware.org/bugzilla/
used rarely

Product cygwin - Component setup.exe
  http://www.sourceware.org/bugzilla/buglist.cgi?product=3Dcygwin&component=
=3Dsetup.exe

I have no idea how one can interface bugzilla or any other tracker to
our package - maintainer list:
  http://cygwin.com/cygwin-pkg-maint
--=20
Reini Urban

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple