diff options
| author | Michael Albinus <michael.albinus@gmx.de> | 2020-08-27 11:46:20 +0200 |
|---|---|---|
| committer | Michael Albinus <michael.albinus@gmx.de> | 2020-08-27 11:46:20 +0200 |
| commit | da4840af120a2b8ac0851fe732336eb8cc33940b (patch) | |
| tree | 34146c8769ee26bbb871233b236388b08423c612 /admin/release-process | |
| parent | eb77572257bfa4e649c0c8852d2d0a58ad63eaa5 (diff) | |
| download | emacs-da4840af120a2b8ac0851fe732336eb8cc33940b.tar.gz | |
Adapt reminder-for-release-blocking-bugs
* admin/admin.el (reminder-for-release-blocking-bugs):
Require `debbugs-gnu' also in `interactive' form.
* admin/release-process: Rename RELEASE-CRITICAL to RELEASE-BLOCKING.
Adapt Emacs version. Describe `reminder-for-release-blocking-bugs'.
Diffstat (limited to 'admin/release-process')
| -rw-r--r-- | admin/release-process | 20 |
1 files changed, 14 insertions, 6 deletions
diff --git a/admin/release-process b/admin/release-process index b3dfad58729..c3728b582f1 100644 --- a/admin/release-process +++ b/admin/release-process @@ -41,17 +41,17 @@ released in the next release cycle. From time to time, the master branches merges bugfix commits from the "emacs-NN" branch. See admin/gitmerge.el. -* RELEASE-CRITICAL BUGS +* RELEASE-BLOCKING BUGS Emacs uses the "blocking" feature of Debbugs for bugs that need to be addressed in the next release. -Currently, bug#39200 is the tracking bug for release of 27.1 and +Currently, bug#43018 is the tracking bug for release of 27.2 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 +to be fixed for Emacs 27.2. Send a message to control@debbugs.gnu.org that says: - block 39200 by 123 + block 43018 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 @@ -59,9 +59,17 @@ 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: +following command to see all bugs which block a given release: - (debbugs-gnu-emacs-release-blocking-reports "27.1") + (debbugs-gnu-emacs-release-blocking-reports "27.2") + +The following command from admin/admin.el sends a reminder message +about release-blocking bugs to the <emacs-devel@gnu.org> mailing list: + + (reminder-for-release-blocking-bugs "27.2") + +It is recommended to send this reminder message once a month. Once the +pretest has started, a reminder message once a week is appropriate. * TO BE DONE SHORTLY BEFORE RELEASE |