From: Mike Frysinger <vapier@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Bugzilla: Requirement for comment with RESOLVED
Date: Mon, 23 May 2016 16:51:00 -0000 [thread overview]
Message-ID: <20160523161009.GM26300@vapier.lan> (raw)
In-Reply-To: <958d7f00-c325-d107-ed20-438cd80b278c@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On 23 May 2016 14:43, Florian Weimer wrote:
> 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?
i tend to agree. if someone wants to misbehave, they can just use "."
to bypass the check (and this has happened in the past).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-23 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 14:14 Florian Weimer
2016-05-23 16:51 ` Mike Frysinger [this message]
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=20160523161009.GM26300@vapier.lan \
--to=vapier@gentoo.org \
--cc=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).