public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: DJ Delorie <dj@redhat.com>
Cc: neroden@twcny.rr.com, <gcc@gcc.gnu.org>
Subject: Re: your RESOLVED->CLOSED changes
Date: Fri, 23 May 2003 19:56:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0305231445160.13914-100000@gandalf.ices.utexas.edu> (raw)
In-Reply-To: <200305231943.h4NJhYG15097@greed.delorie.com>


> I think it would be better to have some automatic VERIFIED->CLOSED
> cron job, which gives the originator N weeks to reject the fix.

We get the majority of reports against _releases_, not snapshots. If 
something's fixed in a snapshot, it might be half a year or more until the 
originator get's to check whether the bug is fixed. I also get the 
impression that most people just use what's on their system, and then it 
might be even longer until she upgrades.

Asking the originator for confirmation that a bug is fixed is plain 
impractical.

I see us dreaming up complicated schemes to make use of the three-state
thing in bugzilla. I would really like that people keep in mind the cost
of maintaining it. Please, everyone, we should realize that we're not
Microsoft that can throw 100 people at a problem. We just don't have them
and I personally will not have the time to close bugs in a two-step
process. I can make much better use of my time, and I also have the
impression that bugzilla has a lot of places where I can spend it on more 
useful things that following an overly complicated workflow.

W.

-------------------------------------------------------------------------
Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                               www: http://www.ices.utexas.edu/~bangerth/


  reply	other threads:[~2003-05-23 19:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23  7:39 Nathanael Nerode
2003-05-23  8:55 ` Giovanni Bajo
2003-05-23  9:36   ` Gerald Pfeifer
2003-05-23 10:19     ` Giovanni Bajo
2003-05-23 14:18       ` Wolfgang Bangerth
2003-05-23 15:47         ` Nathanael Nerode
2003-05-23 19:23           ` Wolfgang Bangerth
2003-05-23 19:46             ` DJ Delorie
2003-05-23 19:56               ` Wolfgang Bangerth [this message]
2003-05-23 20:03                 ` DJ Delorie
2003-05-23 20:14                   ` Wolfgang Bangerth
     [not found]       ` <Pine.LNX.4.44.0305230908020.22023-100000@gandalf.ices.utex as.edu>
2003-05-23 14:19         ` John Anthony Kazos Jr.
2003-05-23 15:41       ` Nathanael Nerode
2003-05-23 15:33   ` Nathanael Nerode
2003-05-23  9:43 ` Joseph S. Myers
     [not found] ` <Pine.LNX.4.53.0305231035220.4682@kern.srcf.societies.cam.a c.uk>
2003-05-23  9:53   ` John Anthony Kazos Jr.
2003-05-23 15:05 ` Daniel Berlin
2003-05-23 15:54   ` Nathanael Nerode
  -- strict thread matches above, loose matches on Subject: below --
2003-05-23 15:29 Volker Reichelt
2003-05-23 16:18 ` Daniel Berlin
2003-05-23 19:23   ` Wolfgang Bangerth
2003-05-23 19:37   ` DJ Delorie
2003-05-23 14:55 Wolfgang Bangerth
     [not found] <20030523062858.322.qmail@sources.redhat.com>
2003-05-23  6:59 ` Giovanni Bajo

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=Pine.LNX.4.44.0305231445160.13914-100000@gandalf.ices.utexas.edu \
    --to=bangerth@ices.utexas.edu \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    /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).