From: Kaushal Modi <kaushal.modi@gmail.com>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: More tags/usertags on Debbugs?
Date: Fri, 8 Jan 2016 23:10:58 -0500 [thread overview]
Message-ID: <CAFyQvY3=MC+EjAMWJ-mhfyn4Zn+rBRRYBoYkkrWkZeZK=F8EAw@mail.gmail.com> (raw)
In-Reply-To: <CAAF+z6EsUQLTjTU8YSfc-jbpGTCjUGKCftnp+CXVxr961Dz-DA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
> See https://debbugs.gnu.org/Developer#severities .
Thanks!
--
Kaushal Modi
On Jan 8, 2016 10:10 PM, "Xue Fuqiao" <xfq.free@gmail.com> wrote:
> On Sat, Jan 9, 2016 at 10:56 AM, Kaushal Modi <kaushal.modi@gmail.com>
> wrote:
> > When I read the severity levels, I actually wondered if we have more than
> > needed severity tags... How would one distinguish among critical, grave
> and
> > serious severities?
>
> See https://debbugs.gnu.org/Developer#severities .
>
> > The one lower important could be probably understood as an important bug
> to
> > be fixed but that which probably does not block a release.
>
> FYI - we use the "blocking bug(s)" feature of Debbugs (instead of
> severity levels) for release-critical bugs.
>
> See
> http://git.savannah.gnu.org/cgit/emacs.git/tree/admin/release-process?id=9f2f14a0725211b13a744573344636b57b9c98b9#n42
>
[-- Attachment #2: Type: text/html, Size: 1573 bytes --]
next prev parent reply other threads:[~2016-01-09 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 2:53 More tags/usertags on Debbugs? Xue Fuqiao
2016-01-09 2:56 ` Kaushal Modi
2016-01-09 3:10 ` Xue Fuqiao
2016-01-09 4:10 ` Kaushal Modi [this message]
2016-01-09 9:26 ` Michael Albinus
2016-01-10 5:27 ` Xue Fuqiao
2016-01-09 7:32 ` Eli Zaretskii
2016-01-11 19:39 ` John Wiegley
2016-01-11 19:57 ` Michael Albinus
2016-01-09 7:24 ` Eli Zaretskii
2016-01-10 5:22 ` Xue Fuqiao
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='CAFyQvY3=MC+EjAMWJ-mhfyn4Zn+rBRRYBoYkkrWkZeZK=F8EAw@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=xfq.free@gmail.com \
/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).