From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message
Date: Sun, 25 Nov 2007 15:02:13 +0100 [thread overview]
Message-ID: <47498065.5070203@wpkg.org> (raw)
Rafael J. Wysocki wrote:
(...)
>> * After each major kernel release bugzilla should send a kind request for
>> retesting to all open bugs.
>
> Good idea, IMO.
Another alternative would be to send such a request if a given bug had
no activity for, say, 6 months.
(...)
>> * Last but not least our bugzilla just looks ugly (it is _very_ important,
>> I feel disgusted each time I have to work with it, OTOH I love using
>> gitweb - you get the idea).
>
> Well, that doesn't matter to me as long as it's useful. Any ideas how to
> improve that? ;-)
Upgrade to Bugzilla 3.0.x. Its interface looks a bit better (and has a
handful of useful features).
(...)
>> Hmm, what about switching to some proprietary bug tracking system just to
>> talk Linus into writing a superior one? ;-)
>
> I think that we just have to get an idea of what exactly is needed. IOW, we
> need to know exactly how we're going to handle bugs as much as we needed
> to know exactly how we were going the handle the flow of changes.
> Perhaps it would be necessary to use a proprietary bug tracking system for some
> time for this purpose, but _maybe_ we can figure it out without anything like
> that.
How do others track bugs for software projects? RedHat, Novell, IBM,
others - anyone reading this thread?
--
Tomasz Chmielewski
http://wpkg.org
reply other threads:[~2007-11-25 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47498065.5070203@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.