unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: 20389@debbugs.gnu.org
Subject: bug#20389: A way to communicate announcements to developers
Date: Mon, 20 Apr 2015 17:56:23 -0400	[thread overview]
Message-ID: <ysfv7uwjjs.fsf@fencepost.gnu.org> (raw)

Package: emacs
Severity: wishlist
Version: 24.5

(Bug report to remind about
http://lists.gnu.org/archive/html/emacs-devel/2014-12/msg00851.html)

Please create a mechanism to communicate important announcements
(feature freezes, etc) to emacs developers.
No-one should have to read (all of) emacs-devel, it's too noisy.
And the info-gnu-emacs list is not appropriate for this IMO.

FWIW, here's what I would do. It'd only take a few mins to set up:

1. Go to https://lists.gnu.org/mailman/admin/emacs-devel/topics

2. Enable topic filter.

3. Add topic name "emacs-announce"; regexp "emacs-announce"; description
"announcements all Emacs developers should read".
(Using just "announce" may lead to false positives?)

4. Document that developers should subscribe to emacs-devel and at
least subscribe to the "emacs-announce" topic. Whether or not they also
choose to "receive messages that do not match any topic filter" is up
to the individual.

5. Use "Keywords: emacs-announce" in the header of relevant mails.
Better (?) to use keywords: than the subject: header, to avoid all the
replies to said subject being sent out as announcements too. If you
forget to add it to a message, you or anyone else can just resend it.





             reply	other threads:[~2015-04-20 21:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 21:56 Glenn Morris [this message]
2015-04-21  1:20 ` bug#20389: A way to communicate announcements to developers Stefan Monnier
2015-04-22 17:18   ` Glenn Morris
2015-04-22 20:53     ` Stefan Monnier
2015-04-21 16:32 ` Eli Zaretskii
2015-04-21 17:22   ` Andreas Schwab
2015-04-21 18:37     ` Eli Zaretskii
2015-04-22 17:21       ` Glenn Morris
2015-04-22 17:50         ` Eli Zaretskii
2015-04-24 18:29           ` Glenn Morris

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=ysfv7uwjjs.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=20389@debbugs.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).