A way to communicate announcements to developers

A way to communicate announcements to developers

[Glenn Morris]

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.

It's not reasonable to expect all developers to follow this (very noisy)
list to get such information.
(I'm considering disabling my subscription; I think I'd get more done.)

RE: A way to communicate announcements to developers

[Mirek Kaim]

> From: rgm@gnu.org
> To: emacs-devel@gnu.org
> Subject: A way to communicate announcements to developers
> Date: Mon, 8 Dec 2014 12:16:21 -0500
>
>
> 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.
>
> It's not reasonable to expect all developers to follow this (very noisy)
> list to get such information.
> (I'm considering disabling my subscription; I think I'd get more done.)
>

perhaps silly idea, but how about empty commits? just a message, and predefined - always the same - author.
devs can be expected to keep up with the source tree, so i guess it could work.


unic0rn

 		 	   		  

Re: A way to communicate announcements to developers

[Lars Magne Ingebrigtsen]

Glenn Morris <rgm@gnu.org> writes:

> (I'm considering disabling my subscription; I think I'd get more done.)

What about just kill-filing all threads that have certain participants
that are longer than 5 messages?  That gets the blood pressure down.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: A way to communicate announcements to developers

[Stefan Monnier]

> 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.


        Stefan

Re: A way to communicate announcements to developers

[Stephen Leake]

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