From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, 39200@debbugs.gnu.org
Subject: bug#39200: Release 27.1
Date: Mon, 24 Aug 2020 18:05:53 +0200 [thread overview]
Message-ID: <874kosghb2.fsf@gmx.de> (raw)
In-Reply-To: <83k0xp6tcj.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Aug 2020 22:43:40 +0300")
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> I could add a script to the debbugs package, which will do the dirty
>> steps collecting data and preparing the message. Activation shall still
>> be performed manually, by whomever feels ready.
>
> Fine with me, thanks.
Finally, I've added the command `reminder-for-release-critical-bugs' to
admin/admin.el of the emacs-27 branch. See appended patch.
Comments, especially about the wording of the message, are welcome.
Best regards, Michael.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 2754 bytes --]
*** /tmp/ediffR9vehu 2020-08-24 18:00:11.883133992 +0200
--- /home/albinus/src/emacs-27/admin/admin.el 2020-08-24 17:56:38.271440689 +0200
***************
*** 921,926 ****
--- 921,978 ----
'help-echo "Mouse-2: visit this definition"
:type 'cusver-xref)))))))
+ \f
+ ;; Reminder message for open release-critical bugs. This requires the
+ ;; GNU ELPA package `debbugs'.
+
+ (defun reminder-for-release-critical-bugs (version)
+ "Submit a reminder message for release critical bugs of Emacs VERSION."
+ (interactive
+ (list (read-string "Version number: "
+ (pcase (nbutlast (version-to-list emacs-version)
+ ;; Chop off build number, if needed.
+ (if (boundp 'emacs-build-number)
+ 0 1))
+ (`(,major ,minor ,_micro) ; Development version.
+ (format "%d.%d" major (1+ minor)))
+ (`(,major ,minor) ; Release version.
+ (format "%d.%d" major minor))
+ ;; Unexpected version format?
+ (_ emacs-version)))))
+
+ (require 'reporter)
+ (require 'debbugs-gnu)
+
+ (when-let ((id (alist-get version debbugs-gnu-emacs-blocking-reports
+ nil nil #'string-equal))
+ (status-id (debbugs-get-status id))
+ (blockedby-ids (debbugs-get-attribute (car status-id) 'blockedby))
+ (blockedby-status
+ (apply #'debbugs-get-status (sort blockedby-ids #'<))))
+
+ (reporter-submit-bug-report
+ "<emacs-devel@gnu.org>" ; to-address
+ nil nil nil
+ (lambda () ; posthook
+ (goto-char (point-min))
+ (mail-position-on-field "subject")
+ (insert (format "Release-critical bugs for Emacs %s" version))
+ (mail-text)
+ (delete-region (point) (point-max))
+ (insert "
+ The following bugs are regarded as release-critical for Emacs " version ".
+ People are encouraged to work on them with priority.\n\n")
+ (dolist (_ blockedby-status)
+ (unless (equal (debbugs-get-attribute _ 'pending) "done")
+ (insert (format "bug#%d %s\n"
+ (debbugs-get-attribute _ 'id)
+ (debbugs-get-attribute _ 'subject)))))
+ (insert "
+ 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 \"" version "\")\n")))))
+
(provide 'admin)
;;; admin.el ends here
next prev parent reply other threads:[~2020-08-24 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tv4qxr2x.fsf@gmx.de>
[not found] ` <handler.39200.Q.157952248126501.ackquiet@debbugs.gnu.org>
2020-08-23 13:26 ` bug#39200: Release 27.1 Stefan Kangas
2020-08-23 17:16 ` Michael Albinus
2020-08-23 18:44 ` Eli Zaretskii
2020-08-23 18:57 ` Michael Albinus
2020-08-23 19:01 ` Eli Zaretskii
2020-08-23 19:10 ` Michael Albinus
2020-08-23 19:13 ` Eli Zaretskii
2020-08-23 19:23 ` Michael Albinus
2020-08-23 19:43 ` Eli Zaretskii
2020-08-24 16:05 ` Michael Albinus [this message]
2020-08-24 16:11 ` Eli Zaretskii
2020-08-24 16:15 ` Michael Albinus
2020-08-23 22:58 ` Dmitry Gutov
2020-08-24 4:58 ` Eli Zaretskii
2020-08-23 19:06 ` Stefan Kangas
2020-08-23 19:17 ` Michael Albinus
2020-08-23 19:56 ` Stefan Kangas
2020-08-23 23:06 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kosghb2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=39200@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.