automake-patches
[Top][All Lists]
Advanced

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

[FYI] {maint} HACKING: release process: fixlets about the announcement


From: Stefano Lattarini
Subject: [FYI] {maint} HACKING: release process: fixlets about the announcement
Date: Sat, 15 Dec 2012 18:09:45 +0100

* HACKING: The announcement should be generate *before* bumping
the version number to the next alpha number.  Also, only an
abridged version of the announcement should be copied on the
Savannah news feed (a link to the complete announcement should
be linked from there, though).

Signed-off-by: Stefano Lattarini <address@hidden>
---
 HACKING | 24 ++++++++++++++----------
 1 file changed, 14 insertions(+), 10 deletions(-)

diff --git a/HACKING b/HACKING
index 4641d90..5dadf1b 100644
--- a/HACKING
+++ b/HACKING
@@ -280,23 +280,27 @@
   - Check for link errors, fix them, recheck until convergence:
     <http://validator.w3.org/checklink>
 
+* Create an announcement message with "make announcement".  Edit the
+  generated 'announcement' file appropriately, in particularly filling
+  in by hand any "TODO" left in there.
+
 * Update version number in configure.ac to next alpha number.
   Re-run ./bootstrap.sh and commit.
 
 * Don't forget to "git push" your changes so they appear in the public
   git tree.
 
-* Create an announcement message with "make announcement".  Edit the
-  generated 'announcement' file appropriately, in particularly filling
-  in by hand any "TODO" left in there.
-
-* Send the announcement at least to <address@hidden> and
-  <address@hidden>.  If the release is a stable one, the announcement
-  must also go to <address@hidden>; if it is an alpha or beta release,
-  announcement should be sent also to <address@hidden>, to
-  maximize the possibility of early testing on exotic or proprietary
-  systems.  Finally, copy the announcement into the NEWS feed at
+* Send the announcement generated in the earlier steps at least to
+  <address@hidden> and <address@hidden>.  If the release
+  is a stable one, the announcement must also go to <address@hidden>;
+  if it is an alpha or beta release, announcement should be sent also
+  to <address@hidden>, to maximize the possibility of early
+  testing on exotic or proprietary systems.  Finally, copy an abridged
+  version of the announcement into the NEWS feed at:
   <https://savannah.gnu.org/projects/automake>.
+  Be sure to link a  version to the complete announcement (from
+  the version you sent to the automake list, as get archived on
+  <http://lists.gnu.org/archive/html/automake/>).
 
 -----
 
-- 
1.8.0.1.347.gf94c325




reply via email to

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