From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: A way to communicate announcements to developers
Date: Mon, 08 Dec 2014 17:55:14 -0600 [thread overview]
Message-ID: <857fy1bst9.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwvk322yngb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 08 Dec 2014 14:05:09 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Please set up a mechanism to communicate important announcements
>> (feature freezes, all documentation now to be in esperanto, that kind of
>> thing) to developers. It's been discussed before but nothing ever
>> happened. I still favour an emacs-devel Mailman "announce" topic, but
>> anything will do, so please don't spend ages discussing the very best
>> way. A web page to check, whatever.
>
> I think gnu.emacs.announce would work just fine for that, actually.
> We normally only use it to announce releases, so we shouldn't add too
> many messages in there. But announcing the feature-freezes sounds OK.
+1.
That gives us a small archive to check, even if we are not monitoring
the list continuously.
Hmm. Except that's a newsgroup; is it archived somewhere official (ie
other than Google groups)?
The Savannah list of Emacs newsgroups at
https://savannah.gnu.org/mail/?group_id=40 says info-gnu-emacs is for
announcements. It currently has announcements of pretests and release
candidates, as well as some ELPA package releases.
Ah; it looks like gnu.emacs.announce is a mirror of that mailing list
(or vice versa).
--
-- Stephe
prev parent reply other threads:[~2014-12-08 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 17:16 A way to communicate announcements to developers Glenn Morris
2014-12-08 18:22 ` Mirek Kaim
2014-12-08 18:24 ` Lars Magne Ingebrigtsen
2014-12-08 19:05 ` Stefan Monnier
2014-12-08 23:55 ` Stephen Leake [this message]
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=857fy1bst9.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@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 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.