[SCM] GNU Libtool branch, master, updated. v2.2.4-52-g5eaa40f

[Gary V. Vaughan]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Libtool".

The branch, master has been updated
       via  5eaa40f7f6f6f00acd4dc144e206b501a3167bbb (commit)
      from  96e199bd5142ebd542e587d5f3379d1e762b3ff7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5eaa40f7f6f6f00acd4dc144e206b501a3167bbb
Author: Gary V. Vaughan <address@hidden>
Date:   Sun Sep 7 19:59:28 2008 +0800

    Retire gnu.org news.html in favour of savannah news.
    * HACKING (Release Procedure): Add instructions for sending
    a web release announcement to http://planet.gnu.org via
    the savannah news manager.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog |    5 +++++
 HACKING   |   12 +++++++-----
 2 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 7ac504c..d62d219 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2008-09-07  Gary V. Vaughan  <address@hidden>
 
+       Retire gnu.org news.html in favour of savannah news.
+       * HACKING (Release Procedure): Add instructions for sending
+       a web release announcement to http://planet.gnu.org via
+       the savannah news manager.
+
        Add untested git push conflict testing to commit script.
        * clcommit.m4sh (func_check_conflicts): Test return status
        of 'git push --dry-run', and display an error on non-zero.
diff --git a/HACKING b/HACKING
index 10d4bb3..346ad15 100644
--- a/HACKING
+++ b/HACKING
@@ -719,9 +719,6 @@ or obtained by writing to the Free Software Foundation, 
Inc.,
   an alpha release destined for alpha.gnu.org, then the files should be
   placed in the /incoming/alpha directory.
 
-* Send announcement to address@hidden and address@hidden,
-  if not an alpha send to address@hidden as well.
-
 * Update version number in configure.ac and libltdl/configure.ac to next
   alpha number.  See http://www.gnu.org/software/libtool/contribute.html
   for details of the numbering scheme.
@@ -731,13 +728,18 @@ or obtained by writing to the Free Software Foundation, 
Inc.,
 * Run ./commit.
 
 * Update the webpages, libtool.html will need to indicate the latest
-  release number and the news page should get a HTMLified copy of your
-  release announcement.
+  release number.
 
 * If not an alpha, upload new manual pages with cvs to:
   <yourusername>@cvs.savannah.gnu.org:/webcvs/libtool
   (generate with `make -f[../]Makefile.maint web-manual').
 
+* Send announcement to address@hidden and address@hidden,
+  if not an alpha send to address@hidden as well.
+
+* Post a copy of the release announcement to savannah news:
+  https://savannah.gnu.org/news/submit.php?group=libtool
+  which will automatically propogate to http://planet.gnu.org.
 
 
 13. Alpha release note template


hooks/post-receive
--
GNU Libtool