diff options
| author | Michael Albinus <michael.albinus@gmx.de> | 2020-01-20 16:32:13 +0100 |
|---|---|---|
| committer | Michael Albinus <michael.albinus@gmx.de> | 2020-01-20 16:32:13 +0100 |
| commit | 154cd116be38fd9666484cca9d3f08827d25dd66 (patch) | |
| tree | 85e855f50ad8a66f59c1701626b071f1750a93c7 /admin/release-process | |
| parent | fd192821342dee6692068adcb18342674f701bc8 (diff) | |
| download | emacs-154cd116be38fd9666484cca9d3f08827d25dd66.tar.gz | |
* admin/release-process: Adapt bug numbers for release critical bugs.
Mention debbugs-gnu-emacs-release-blocking-reports.
Diffstat (limited to 'admin/release-process')
| -rw-r--r-- | admin/release-process | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/admin/release-process b/admin/release-process index 504b70270f8..b3dfad58729 100644 --- a/admin/release-process +++ b/admin/release-process @@ -46,18 +46,22 @@ See admin/gitmerge.el. Emacs uses the "blocking" feature of Debbugs for bugs that need to be addressed in the next release. -Currently, bug#21966 is the tracking bug for release of 25.2 and -bug#24655 is the tracking bug for release 26.1. Say bug#123 needs -to be fixed for Emacs 26.1. Send a message to control@debbugs.gnu.org +Currently, bug#39200 is the tracking bug for release of 27.1 and +bug#39202 is the tracking bug for release 28.1. Say bug#123 needs +to be fixed for Emacs 27.1. Send a message to control@debbugs.gnu.org that says: - block 24655 by 123 + block 39200 by 123 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 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. +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 |