unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Classifying bugs
Date: Wed, 25 Mar 2009 02:30:06 -0400	[thread overview]
Message-ID: <kpwsaexggh.fsf@fencepost.gnu.org> (raw)
In-Reply-To: jwvbprqe6ny.fsf-monnier+emacs@gnu.org

Stefan Monnier wrote:

> In order to prepare for Emacs-23, we need to start sorting out the bugs
> that need to be fixed.  For this, the best thing to do is to mark bugs
> in the bug-tracker with the `critical' severity.

I would suggest that "serious" is better:

i) It fits in with the standard debbugs definitions
(http://emacsbugs.donarmstrong.com/Developer#severities)

ii) It leaves room to classify security holes, data loss bugs, etc as
really "critical".


Also, you need to provide some guidelines, else this will be subjective.
For Emacs 22.1, almost any bug was release-blocking.
As a specific example, is any nextstep-only issue a "critical" bug to you?
(Presumably not, given than 620 isn't.)




      reply	other threads:[~2009-03-25  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  1:31 Classifying bugs Stefan Monnier
2009-03-25  6:30 ` Glenn Morris [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=kpwsaexggh.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).