This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug web/66802] Some of the Bugzilla Bug fields descriptions do not reflect GCC development
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 08 Jul 2015 09:11:24 +0000
- Subject: [Bug web/66802] Some of the Bugzilla Bug fields descriptions do not reflect GCC development
- Auto-submitted: auto-generated
- References: <bug-66802-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66802
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-07-08
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to UroÅ Bizjak from comment #0)
> IMO, Priority and Severity fields also need a better description - at least
> the criteria for Priority and Severity selections, and who can set these
> fields (Release Managers?).
IMHO those fields should not even be shown on the New Bug form. Even if we
document how they should be used we're still going to get users selecting
"Blocker" because the bug means they can't deliver their work on time.
The ideal might be to only show them (and allow them to be edited on existing
bugs) by people with an @gcc.gnu.org email address.