Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <4161B73C.5050601@x-ray.at>
Date: Mon, 04 Oct 2004 22:49:00 +0200
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a3) Gecko/20040817
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: whole cygwin release/ distribution issues
References: <NUTMEGw6lJiwOjseAdF0000023c AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <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> <20041004202743 DOT GE1905 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20041004202743.GE1905@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Christopher Faylor schrieb:
> 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.

Ok. Just an additional entry in the "Product" list
at https://bugzilla.redhat.com/bugzilla/

Ok, I volunteer to admin this.
Though I believe someone with shell acces to bugzilla could do it better:
* setup maintainer accounts,
* automatic mail to package maintainer on tracker updates,
* automatic sync with some TBD package maintainership
   package - email list
* automatic sync of the bugzilla Cygwin Components with
   the package list.

My account is this email account of mine.
Maybe other developers are interested also.

Product: add "Cygwin"

Version:
   Should probably be based on the cygwin dll versions:
          1.3.x
          1.5.10
          1.5.11
          latest snapshot

The Components have to be synched with the package list (setup.ini). 
This should be done automatically.
The rest can stay as is.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

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