From: Florian Weimer <fweimer@redhat.com>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: Bugzilla: Requirement for comment with RESOLVED
Date: Mon, 23 May 2016 14:14:00 -0000 [thread overview]
Message-ID: <958d7f00-c325-d107-ed20-438cd80b278c@redhat.com> (raw)
Currently, Bugzilla is configured to require a comment for a transition
to RESOLVED. Previously, this was only enforced for some RESOLVED
combinations (such as RESOLVED/FIXED). But now it seems to be required
for all states, including RESOLVED/INVALID.
Is this really what we want? I assume closing other people's bugs
requires editbugs group membership, and we can probably trust those
people to add a comment when necessary.
What do you think? Should we get rid of the RESOLVED-needs-comment
requirement?
Thanks,
Florian
next reply other threads:[~2016-05-23 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 14:14 Florian Weimer [this message]
2016-05-23 16:51 ` Mike Frysinger
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=958d7f00-c325-d107-ed20-438cd80b278c@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).