update from texinfo

[gnulib.git] / doc / maintain.texi

diff --git a/doc/maintain.texi b/doc/maintain.texi
index e67955d..b91b5e7 100644 (file)
--- a/doc/maintain.texi
+++ b/doc/maintain.texi
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
-@set lastupdate August 1, 2008
+@set lastupdate October 13, 2008
 @c %**end of header
 
 @dircategory GNU organization
@@ -1207,7 +1207,7 @@ before they are made publicly available.
 @node Automated Upload Registration
 @subsection Automated Upload Registration
 
-@cindex registration
+@cindex registration for uploads
 @cindex uploads, registration for
 
 Here is how to register your information so you can perform uploads
@@ -1310,6 +1310,18 @@ are sent a message if there are any problems processing an upload for your
 package. You also receive a message when your upload has been successfully
 processed.
 
+One relatively easy way to create and transfer the necessary files is
+to use the @code{gnupload} script, which is available from the
+@file{build-aux/} directory of the @code{gnulib} project at
+@url{http://savannah.gnu.org/projects/gnulib}.  Run @code{gnupload
+--help} for a description and examples.
+
+@code{gnupload} uses the @code{ncftpput} program to do the actual
+transfers; if you don't happen to have the @code{ncftp} package
+installed, you can use the @code{ncftpput-ftp} script as a
+replacement, which uses plain command line @code{ftp}.  It's also
+available from the @file{build-aux/} directory of @code{gnulib}.
+
 If you have difficulties processing an upload, email
 @email{ftp-upload@@gnu.org}.
 
@@ -1454,20 +1466,32 @@ your package (in the example above, that is @code{bar}).
 
 @node Announcements
 @section Announcing Releases
+@cindex announcements
 
+@cindex @code{info-gnu} mailing list
 When you have a new release, please make an announcement.  For
 official new releases, including those made just to fix bugs, we
-recommend using the (moderated) general GNU announcements list,
-@email{info-gnu@@gnu.org}.  Doing so makes it easier for users and
-developers to find the latest GNU releases.  On the other hand, please
-do not announce test releases on @code{info-gnu} unless it's an
+strongly recommend using the (moderated) general GNU announcements
+list, @email{info-gnu@@gnu.org}.  Doing so makes it easier for users
+and developers to find the latest GNU releases.  On the other hand,
+please do not announce test releases on @code{info-gnu} unless it's an
 unusual situation.
 
+@cindex @url{http://planet.gnu.org}
+@cindex Savannah, news area
+Please also post release announcements in the news section of your
+Savannah project site.  It is fine to also write news entries for test
+releases and any other newsworthy events.  The news feeds from all GNU
+projects at savannah are aggregated at @url{http://planet.gnu.org}.
+(You can also post items directly, or arrange for feeds from other
+locations; see contact information on the GNU Planet web page.) 
+
+@cindex announcement mailing list, project-specific
 You can maintain your own mailing list (typically
 @email{info-@var{program}@@gnu.org}) for announcements as well if you
-like.  For your own list, you can decide as you see fit what events
-are worth announcing.  (@xref{Mail}, for more suggestions on handling
-mail for your package.)
+like.  For your own list, of course you can decide as you see fit what
+events are worth announcing.  (@xref{Mail}, for more suggestions on
+handling mail for your package.)
 
 
 @node Web Pages