public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/23281] Miscategorization of quality-of-implementation reports Date: Mon, 08 Aug 2005 03:00:00 -0000 [thread overview] Message-ID: <20050808030018.30096.qmail@sourceware.org> (raw) In-Reply-To: <20050808024133.23281.igodard@pacbell.net> ------- Additional Comments From dberlin at gcc dot gnu dot org 2005-08-08 03:00 ------- (In reply to comment #0) > > Consequently I'm filing this DR against the gcc DR reporting machinery itself, > rather than against the compiler in particular. There needs to be categories for > QOI defects of varying severity; No. Speaking as the bugzilla person, i'm not adding categories for QOI issues, because almost everything that isn't a strict bug is a QOI issue already. Diagnostic issues should be filed against the approriate frontend component, or middle-end/backend (in a few cases). I am also not going to add 57 different severities, because it wouldn't do anything for people trying to fix bugs. Read the details of what the severities show (click the linked word severity), and you will see that most diagnostic issues do indeed fall under enhancement. People subjectively view the severity of an issue differently, which is why we have people go through and evaluate it using the objective criteria in the management page. > either that, or complaints about diagnostics > and other QOI ussues should not by policy be filed as "enhancement requests", > and forgotten. If they are forgotten, it is not because they are marked enhancement requests as opposed to minor or normal. You are mixing up severity and priority. Severity is basically an objective measure. Priority is a subjective measure, and theoretically used by developers to prioritize which bugs to work on. . -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23281
prev parent reply other threads:[~2005-08-08 3:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-08 2:41 [Bug other/23281] New: " igodard at pacbell dot net 2005-08-08 2:48 ` [Bug other/23281] " pinskia at gcc dot gnu dot org 2005-08-08 3:00 ` dberlin at gcc dot gnu dot org [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=20050808030018.30096.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).