public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Phil Richards <news@derived-software.ltd.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] What is classified as a "blocker" bug?
Date: Tue, 30 Sep 2003 18:58:33 +0100 (BST)	[thread overview]
Message-ID: <20030930175833.DA9208C01C@derisoft.derived-software.demon.co.uk> (raw)

I try to make sure that when I file a bug on bugs.gentoo.org
that I set an "appropriate" severity.

Recently, I tried to emerge glademm with gcc 3.3.1 and it
failed to compile.  I felt that given the description of
severities in the bugzilla:

Blocker         Blocks development and/or testing work
Critical        crashes, loss of data, severe memory leak
Major           major loss of function
Minor           minor loss of function, or other problem
                where easy workaround is present
Trivial         cosmetic problem like misspelled words
                or misaligned text
Enhancement     Request for enhancement

then the appropriate severity is "Blocker".

Clearly, I was wrong because it got downgraded to a "major" -
I suspect that this was because I gave a hacky workaround.

Fair enough.  But could somebody please clarify what the
severities *really* mean?  Preferably on bugzilla itself.
(Given the above descriptions, I would have expected a
downgrade based on having a workaround to be "minor", so
I'm doubly confused.)

I don't actually care what severity is used - but I do like
to get the right one.  Or should I just not bother setting
it in future?

phil
-- 
change name before "@" to "phil" for email


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-09-30 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 17:58 Phil Richards [this message]
2003-09-30 18:34 ` [gentoo-dev] What is classified as a "blocker" bug? Jon Portnoy
2003-09-30 19:09   ` 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=20030930175833.DA9208C01C@derisoft.derived-software.demon.co.uk \
    --to=news@derived-software.ltd.uk \
    --cc=gentoo-dev@gentoo.org \
    --cc=spams@derived-software.demon.co.uk \
    /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