From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_DYNAMIC autolearn=unavailable autolearn_force=no version=4.0.0 Received: from brazil.sys.kcco.com (leg-66-247-92-2-CHI.sprinthome.com [66.247.92.2]) by chiba.3jane.net (Postfix) with ESMTP id 50071AC43F for ; Wed, 24 Jul 2002 06:44:58 -0500 (CDT) Received: from brazil.sys.kcco.com (localhost [127.0.0.1]) by brazil.sys.kcco.com (Postfix) with ESMTP id E2DBEC78F9E; Wed, 24 Jul 2002 06:47:15 -0500 (CDT) Content-Type: text/plain; charset="iso-8859-1" From: Jean-Michel Smith To: Kim Nielsen , gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity Date: Wed, 24 Jul 2002 06:47:14 -0500 User-Agent: KMail/1.4.2 References: <3D3DDE5A.2080909@gentoo.org> <1027498424.28440.13.camel@knielsen> In-Reply-To: <1027498424.28440.13.camel@knielsen> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200207240647.14935.jsmith@kcco.com> Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 2ea48ab5-3ab3-4c99-9509-e59a94ee1619 X-Archives-Hash: e625a896a31241b2c4466696bcfd0c8a On Wednesday 24 July 2002 03:13 am, Kim Nielsen wrote: > Excuse me for sounding a bit grumpy .. but every time I add something > new in bugzilla its stays in bugzilla and no one is using or looking at > it (I submitted a bugfix to the gentoo security guide more than one > month ago). This is how it works with documentation. > > So problems are resolved in the same tempo as with documentation, I can > understand why someone with problems compiling a package prefers to mai= l > it to the list instead of filling out a bug report. I've submitted two bug reports (that I recall). One was fixed and resolved very quickly, the other is being worked on (an= d I=20 periodically receive email detailing the work). The one that hasn't been= =20 resolved yet is a really difficult one (OmniORB's f*cked up installation=20 procedure, which having tried to fix myself and failed I can understand t= he=20 delay on ... working with those .mk scripts is a pain to the nth degree),= but=20 even it is being worked on. Both of the bugs in question were not critical to the overall functionali= ty of=20 the gentoo system ... they were for ebuilds I happen to want to use, that= =20 were (or in the case of omniORB, still are) broken. Critical bugs get fi= xed=20 much faster. It may take a couple or three weeks, but the bug reports do get read,=20 assigned, and fixed. Of course, if the reports are just sent to the list= and=20 complained about, but never filed with bugzilla, it is entirely possible=20 they'll never get fixed. The developers have made it plain on more than = one=20 occasion that the mailing lists and forums are in general a bad place to = be=20 filing bug reports. Jean.