public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: Bugzilla: number of bugs, milestones
Date: Thu, 22 May 2003 00:42:00 -0000	[thread overview]
Message-ID: <4B6CB206-8BE2-11D7-AF07-000A95A34564@dberlin.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0305212244070.10353@kern.srcf.societies.cam.ac.uk>


On Wednesday, May 21, 2003, at 05:49  PM, Joseph S. Myers wrote:

> (1) Doing an empty search query shows 1620 open bugs.  The weekly bug
> summary shows 1298, but I doubt we've been down that low in the past 
> week.
> Have we really been that low, or is there some other reason for the
> difference?
Weekly bug summary isn't including WAITING/SUSPENDED
I've fixed it.

there are approximately 56 SUSPENDED bugs, and 266 WAITING bugs.
1298+322 = 1620

>
> (2) Lots of bugs seem to be set to the 3.4 milestone, without any
> indication in the comments that they are a regression, e.g. 1016.  Why?

It was the  default milestone.

> Bugs marked as a regression should be set to appropriate milestones
> (3.3.1/3.4 according to whether the regression is present in 3.3) but a
> lot of these don't seem to have any reason to have a milestone set.

I can remove the milestone from all bugs if you like, and people can 
re-set it where approriate.

  reply	other threads:[~2003-05-21 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 21:55 Joseph S. Myers
2003-05-22  0:42 ` Daniel Berlin [this message]
2003-05-22  6:51   ` Joseph S. Myers

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=4B6CB206-8BE2-11D7-AF07-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).