emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] emacs-26 6f43d29: ; * CONTRIBUTE, admin/make-tarball.txt:


From: Glenn Morris
Subject: [Emacs-diffs] emacs-26 6f43d29: ; * CONTRIBUTE, admin/make-tarball.txt: Doc tweaks re 'emacs-announce'.
Date: Fri, 3 Nov 2017 15:55:43 -0400 (EDT)

branch: emacs-26
commit 6f43d29d29605b710e51ff7f1487063c2f5b0b5a
Author: Glenn Morris <address@hidden>
Commit: Glenn Morris <address@hidden>

    ; * CONTRIBUTE, admin/make-tarball.txt: Doc tweaks re 'emacs-announce'.
---
 CONTRIBUTE             | 9 +++++----
 admin/make-tarball.txt | 5 +++++
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/CONTRIBUTE b/CONTRIBUTE
index c7f3330..c324375 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -27,10 +27,11 @@ admin/notes/git-workflow.
 ** Getting involved with development
 
 Discussion about Emacs development takes place on address@hidden
-You can subscribe to the address@hidden mailing list, paying
-attention to postings with subject lines containing "emacs-announce",
-as these discuss important events like feature freezes.  See
-https://lists.gnu.org/mailman/listinfo/emacs-devel for mailing list
+You can subscribe to the address@hidden mailing list.
+If you want to get only the important mails (for things like
+feature freezes), choose to receive only the 'emacs-announce' topic
+(although so far this feature has not been well or consistently used).
+See https://lists.gnu.org/mailman/listinfo/emacs-devel for mailing list
 instructions and archives.  You can develop and commit changes in your
 own copy of the repository, and discuss proposed changes on the
 mailing list.  Frequent contributors to Emacs can request write access
diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt
index 466ee09..6d6312c 100644
--- a/admin/make-tarball.txt
+++ b/admin/make-tarball.txt
@@ -177,6 +177,11 @@ General steps (for each step, check for possible errors):
     See the info-gnu-emacs mailing list archives for the form
     of past announcements.  The first pretest announcement, and the
     release announcement, should have more detail.
+    Use the emacs-devel topic 'emacs-announce'.  The best way to do
+    this is to add a header "Keywords: emacs-announce" to your mail.
+    (You can also put it in the Subject, but this is not as good
+    because replies that invariably are not announcements also get
+    sent out as if they were.)
 
 12. After a release, update the Emacs pages as below.
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]