Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb <gdb@sourceware.org>
Subject: Cleaning out obsolete bugs in bugzilla
Date: Fri, 28 Feb 2014 17:58:00 -0000	[thread overview]
Message-ID: <CADPb22ROq5ieBxJKFpBxOFYx_wSn-FT4A6j5HG1XTVp-O3_n0w@mail.gmail.com> (raw)

Another part of bugzilla spring cleaning (though obviously it's an
ongoing task) I'd like to do is establish a process for closing (in
some form) bugs old enough that the likelihood they will ever get
fixed is within epsilon of zero.  And maybe even closing several of
them.  But as along we we can establish a process for efficiently
closing them (i.e., avoiding drawn out discussions on whether they
should have been closed, and the manor in which they were closed),
then I think we can make better progress at clearing them out (or at
least I know I could ... :-)).

An example of the kind of bug I'm thinking of is this one:
https://sourceware.org/bugzilla/show_bug.cgi?id=8769
gdb 6.1 doesn't build on hpux.

I don't have a strong opinion on what flavor of RESOLVED to close
these as, but I do have a strong opinion that we should close them.  I
can't see any sufficiently significant value to warrant keeping them.

Another bug tracking system I've used has the choice of "Obsolete".
Bugzilla doesn't have it by default but I have confirmed that we can add it.
OTOH, using WONTFIX is fine by me too.  Or we could pick something else.
I'm mentioning the existence of the ability to use something other
than WONTFIX in case people have a strong opinion on not using
WONTFIX.

Comments?


             reply	other threads:[~2014-02-28 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 17:58 Doug Evans [this message]
2014-03-12 16:41 ` Doug Evans
2014-03-12 16:59   ` Pedro Alves
2014-03-12 17:10     ` Doug Evans
2014-03-12 17:24       ` Pedro Alves
2014-03-31 17:42         ` Doug Evans
2014-03-12 17:15     ` Andreas Schwab
2014-03-12 17:22       ` Pedro Alves

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=CADPb22ROq5ieBxJKFpBxOFYx_wSn-FT4A6j5HG1XTVp-O3_n0w@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb@sourceware.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