public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jean-Michel Smith <jsmith@kcco.com>
To: Kim Nielsen <kn@insecurity.dk>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity
Date: Wed, 24 Jul 2002 06:47:14 -0500	[thread overview]
Message-ID: <200207240647.14935.jsmith@kcco.com> (raw)
In-Reply-To: <1027498424.28440.13.camel@knielsen>

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 mail
> 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 (and I 
periodically receive email detailing the work).  The one that hasn't been 
resolved yet is a really difficult one (OmniORB's f*cked up installation 
procedure, which having tried to fix myself and failed I can understand the 
delay on ... working with those .mk scripts is a pain to the nth degree), but 
even it is being worked on.

Both of the bugs in question were not critical to the overall functionality of 
the gentoo system ... they were for ebuilds I happen to want to use, that 
were (or in the case of omniORB, still are) broken.  Critical bugs get fixed 
much faster.

It may take a couple or three weeks, but the bug reports do get read, 
assigned, and fixed.  Of course, if the reports are just sent to the list and 
complained about, but never filed with bugzilla, it is entirely possible 
they'll never get fixed.  The developers have made it plain on more than one 
occasion that the mailing lists and forums are in general a bad place to be 
filing bug reports.

Jean.


  reply	other threads:[~2002-07-24 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 22:53 [gentoo-dev] Bugs Bugs Bugs & Unstablity Doug Goldstein
2002-07-23 23:08 ` Stefano Peluchetti
2002-07-24  7:16 ` Vitaly Kushneriuk
2002-07-24  8:13 ` Kim Nielsen
2002-07-24 11:47   ` Jean-Michel Smith [this message]
2002-07-24 18:31     ` Paul de Vrieze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207240647.14935.jsmith@kcco.com \
    --to=jsmith@kcco.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=kn@insecurity.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox