public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, bugme-admin@osdl.org
Subject: Re: kernel status, 4 Aug 2005
Date: Fri, 5 Aug 2005 14:03:12 +0200	[thread overview]
Message-ID: <20050805120312.GL4029@stusta.de> (raw)
In-Reply-To: <20050805020729.50146221.akpm@osdl.org>

On Fri, Aug 05, 2005 at 02:07:29AM -0700, Andrew Morton wrote:
>...
> Open bugs:
> 
>   This is based on my reading of what's real and of what's worth
>   attending to.  Quite a few things get culled up-front.
> 
>   There are several emailed bug reports which are probably live bugs but
>   they have gone stale hence I have asked the reporters to raise bugzilla
>   reports, so more post-2.6.12 bugs will appear as the reporters retest
>   2.6.13-rc6.
> 
>   I really don't want to have to track bugs which aren't in bugzilla.  If
>   an emailed bug report comes in and we can address it within a few days
>   and a few emails then fine.  If that doesn't happen I'll be asking
>   reporters to open bugzilla reports.
> 
>   All bugs reported prior to the 2.6.12 release have been discarded. 


One thing to note is that this only says that such bugs are no longer on 
your radar. They are still in Bugzilla, and maintainers are still 
encouraged to review and fix them.


>   I'll henceforth track bugs across succeeding major release, so this list
>   will just grow.
> 
>   There are 60 bugs here.  They're almost all post-2.6.12 regressions. 
>   Longer-term we simply have to do better than this, else we'll stabilise
>   at a pretty buggy level.  No matter what process changes we make, the
>   bottom line is that developers/maintainers will need to spend more of
>   their time working with reporters on fixing bugs.
>...


You could track the bugs through Bugzilla.

An advantage would be that everyone can always see which bugs you are 
tracking.

One way would be to (ab)use bug severities
(e.g. severity >= high and number >= 4768).

Another way would be to add bug flags to Bugzilla in a way Mozilla uses 
them [1], IOW a field in the bugs that only you can set.


cu
Adrian

[1] https://bugzilla.mozilla.org/flag-help.html

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2005-08-05 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  9:07 kernel status, 4 Aug 2005 Andrew Morton
2005-08-05 10:22 ` David Vrabel
2005-08-05 10:33   ` Andrew Morton
2005-08-05 20:27     ` Tony Luck
2005-08-05 12:03 ` Adrian Bunk [this message]
2005-08-08 13:59 ` Zilvinas Valinskas

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=20050805120312.GL4029@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=bugme-admin@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox