procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* admin/release-process: Adapt bug numbers for release critical bugs.

Browse source 
Mention debbugs-gnu-emacs-release-blocking-reports.
This commit is contained in:
Michael Albinus 2020-01-20 16:32:13 +01:00
parent fd19282134
commit 154cd116be
1 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
admin/release-process
View file

@ -46,18 +46,22 @@ See admin/gitmerge.el.
Emacs uses the "blocking" feature of Debbugs for bugs that need to be Emacs uses the "blocking" feature of Debbugs for bugs that need to be
addressed in the next release. addressed in the next release.
Currently, bug#21966 is the tracking bug for release of 25.2 and Currently, bug#39200 is the tracking bug for release of 27.1 and
bug#24655 is the tracking bug for release 26.1. Say bug#123 needs bug#39202 is the tracking bug for release 28.1. Say bug#123 needs
to be fixed for Emacs 26.1. Send a message to control@debbugs.gnu.org to be fixed for Emacs 27.1. Send a message to control@debbugs.gnu.org
that says: that says:
block 24655 by 123 block 39200 by 123
Change "block" to "unblock" to remove a bug from the list. Closed Change "block" to "unblock" to remove a bug from the list. Closed
bugs are not listed as blockers, so you do not need to explicitly bugs are not listed as blockers, so you do not need to explicitly
unblock one that has been closed. You may need to force an update of unblock one that has been closed. You may need to force an update of
the tracking bug with ctrl-f5/shift-reload to see the latest version. the tracking bug with ctrl-f5/shift-reload to see the latest version.
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")
* TO BE DONE SHORTLY BEFORE RELEASE * TO BE DONE SHORTLY BEFORE RELEASE