X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 19 Aug 2010 16:49:31 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bug tracker
Message-ID:	<20100819144931.GD19001@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT 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>
MIME-Version:	1.0
In-Reply-To:	<cmfq66p4d2s88u1foj5s7d13ucg2oda29i@4ax.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On Aug 19 10:41, Andrew Schulman wrote:
> > The question is if the maintainers really want that, and cgf and I are
> > just 2 out of ~60 maintainers, maintaining over 1400 packages.  From
> > 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.  If the maintainers
> of those two packages think a bug tracker would be useful, we should make
> one.  If they don't, it's probably not worth bothering.

I do not agree.  On the contrary, I'm under the impression that more and
more mails are reporting packaging problems or generic problems with
using certain packages.  Bash and CRLF in scripts, for instance.
Agreed, at the time of a new Cygwin release breaking things (like this
1.7.6 release), we get more bug reports on Cygwin than usual,

> > How to set that up is YA question.  One category per package?  That
> > doesn't sounds feasible, unless we have another, *active* maintainer
> > just for keeping the bugtracker in shape.
> 
> The list of packages could be automatically fetched and turned into
> categories, once a day.  If the package maintainer names & addresses could
> also be automatically fetched, then they could be automatically propagated
> into the bug tracker too and so much the better.

http://cygwin.com/acronyms/#SHTDI ?

> The UI would need some care.  We would NOT want a pull-down menu of 1400
> categories to enter a new bug :(  An autocomplete widget for the package
> names would probably work well.

Well, most packages are sub-packages.  Like libncurses10 being a subpackage
of ncurses.  We don't need 1400 entries.  Just a couple of hundreds...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

- Raw text -