From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Christian Ehrhardt <ehrhardt@mathematik.uni-ulm.de>,
Giovanni Bajo <giovannibajo@libero.it>,
Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
<S.Bosscher@student.tudelft.nl>, <gcc@gcc.gnu.org>
Subject: Re: Suggestion for a new GNATS policy
Date: Mon, 12 May 2003 14:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0305120916160.15700-100000@gandalf.ices.utexas.edu> (raw)
In-Reply-To: <128EBA6A-8480-11D7-87A1-000A95A34564@dberlin.org>
About the reconfirmed thing:
- Basically, "reconfirmed" is a list of dates of snapshots.
- I'd say everybody agrees that a good approximation to this is a list of
dates at which it was reconfirmed: we may use snapshots that are a
couple of days old, but not more. So let's make it simpler and take the
date/time of reconfirmation, since bugzilla can determine that by
itself.
- Just as much, nobody really cares about previous dates, so it would be
ok to just store the last time something was reconfirmed
Why a separate field (and why we store it in the symposis at present):
- it needs to be visible (see below why); the audit trail is not, at least
not in queries
- reconfirming should be simple; bumping a date was considered simpler
than sending an email
- by point 3 above, nobody cares about previous reconfirmations, so we'd
like not to clutter the audit trails with pages of reconfirmations.
Given the last point, I would very much dislike reconfirming a bug by
clearing-resetting the flag, since that would add _two_ more (and above
that: useless) entries to the audit trail.
My optimal solution would be a button "Reconfirmed" that I could click,
that bumps the date of a respective (queryable) field, and that otherwise
leaves no mark in what I will usually see when I look at the audit trail.
> Developers only care the bug is still valid, remember.
That's too simple, Dan. We are talking about different communities, and
the community that spends the most time with GNATS/bugzilla are what you
termed bugmasters. I tend to think they do valuable work and it would be
unfair to neglect their needs. The "reconfirmed date" information is
clearly important to them (otherwise we wouldn't go to such length to put
it into the synposis of _every single_ C++ report), so please don't make
it harder than necessary.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next prev parent reply other threads:[~2003-05-12 14:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 22:24 Volker Reichelt
2003-05-12 1:56 ` Daniel Berlin
2003-05-12 2:03 ` Giovanni Bajo
2003-05-12 2:23 ` Daniel Berlin
2003-05-12 2:51 ` Giovanni Bajo
2003-05-12 4:16 ` Daniel Berlin
2003-05-12 10:59 ` Christian Ehrhardt
2003-05-12 13:46 ` Daniel Berlin
2003-05-12 14:28 ` Wolfgang Bangerth [this message]
2003-05-12 17:42 ` Daniel Berlin
2003-05-12 18:19 ` Wolfgang Bangerth
2003-05-12 16:36 ` Steven Bosscher
2003-05-12 16:38 ` Wolfgang Bangerth
2003-05-12 13:53 ` Daniel Berlin
2003-05-12 15:10 ` Christian Ehrhardt
2003-05-12 15:57 ` Wolfgang Bangerth
2003-05-12 14:39 ` Wolfgang Bangerth
2003-05-12 16:35 ` Steven Bosscher
2003-05-12 18:04 ` Janis Johnson
2003-05-12 18:57 ` Daniel Berlin
2003-05-12 17:58 ` Daniel Berlin
2003-05-12 18:24 ` Wolfgang Bangerth
2003-05-12 14:48 ` Wolfgang Bangerth
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 16:44 Nathanael Nerode
2003-05-12 16:37 Nathanael Nerode
2003-05-12 16:34 Nathanael Nerode
2003-05-11 21:52 S. Bosscher
2003-05-12 0:58 ` Daniel Berlin
2003-05-12 2:00 ` Giovanni Bajo
2003-05-12 3:10 ` Daniel Berlin
2003-05-12 1:24 ` Daniel Berlin
2003-05-12 14:50 ` Wolfgang Bangerth
2003-05-12 18:56 ` Daniel Berlin
2003-05-11 20:31 Volker Reichelt
2003-05-11 20:46 ` Daniel Berlin
2003-05-11 20:55 ` Joseph S. Myers
2003-05-12 0:51 ` Daniel Berlin
2003-05-12 2:08 ` Giovanni Bajo
2003-05-12 2:40 ` Gabriel Dos Reis
2003-05-12 17:29 ` Janis Johnson
2003-05-12 14:55 ` Wolfgang Bangerth
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.0305120916160.15700-100000@gandalf.ices.utexas.edu \
--to=bangerth@ices.utexas.edu \
--cc=S.Bosscher@student.tudelft.nl \
--cc=dberlin@dberlin.org \
--cc=ehrhardt@mathematik.uni-ulm.de \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=reichelt@igpm.rwth-aachen.de \
/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).