[Bug web/66802] Some of the Bugzilla Bug fields descriptions do not reflect GCC development
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66802 Jonathan Wakely changed: What|Removed |Added Last reconfirmed|2015-07-08 00:00:00 |2017-10-17 --- Comment #2 from Jonathan Wakely --- https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html#bug_status We don't have CONFIRMED or IN_PROGRESS statuses, we have NEW and ASSIGNED. We don't have VERIFIED, we have CLOSED, but the mention of QA in the description is misplaced (there is no QA team for GCC). We also have SUSPENDED and WAITING.
[Bug web/66802] Some of the Bugzilla Bug fields descriptions do not reflect GCC development
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.
