From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Subject: Blocking bugs for Emacs 27.1 and 28.1
Date: Mon, 20 Jan 2020 16:50:24 +0100 [thread overview]
Message-ID: <87v9p6w2in.fsf@gmx.de> (raw)
Hi,
I've created bug#39200 (for Emacs 27.1) and bug#39002 (for Emacs
28.1). These bugs shall keep the bug numbers which are release-critical
for the respective Emacs release. See also admin/release-process about
the procedure.
I've added already the first release-critical bug for Emacs 27.1,
bug#39187. In order to profit best from this approach, I invite
everybody to identify release-critical bugs as described in
admin/release-process. Much more important, of course, is fixing them.
If you use the debbugs package from GNU ELPA, you can apply the
following form to see all bugs which block a given release:
(debbugs-gnu-emacs-release-blocking-reports "27.1")
(New in the just released debbugs 0.22)
Best regards, Michael.
reply other threads:[~2020-01-20 15:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87v9p6w2in.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@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: 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).