[git] GnuPG - branch, master, updated. gnupg-2.1.0beta3-57-g26ec6c7

[by Werner Koch]

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 "The GNU Privacy Guard".

The branch, master has been updated
       via  26ec6c79020c8b3dfd6f517c292bb973209b0d31 (commit)
      from  7ddbcb6b6ab8b26c8e609fcd95c2c8a89bc20a7d (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 26ec6c79020c8b3dfd6f517c292bb973209b0d31
Author: Werner Koch <wk at gnupg.org>
Date:   Tue Mar 27 11:21:33 2012 +0200

    Update the maintenance instructions.
    
    --

diff --git a/README.maint b/README.maint
index bdcdbf9..c317f7c 100644
--- a/README.maint
+++ b/README.maint
@@ -19,34 +19,59 @@ Release process:
 ================
 
   * Make sure that all new PO files are checked in.
+
   * Decide whether you want to update the automake standard files
     (Mainly config.guess and config.sub).
-  * [1.4 only] Update gpg.texi and gpgv.texi from the trunk:
-       make -C doc update-source-from-gnupg-2
-  * [1.4 and 2.0] Copy needed texinfo files from trunk.
-  * Run "make -C po update-po".
+
+  * [1.4 only] Update gpg.texi and gpgv.texi from master:
+      make -C doc update-source-from-gnupg-2
+
+  * [1.4 and 2.0] Copy needed texinfo files from master:
+      make -C doc update-source
+
+  * Run:
+      make -C po update-po
+
   * Write NEWS entries and set the release date in NEWS.
-  * In configure.ac set "my_issvn" to "no".
-  * Commit all changes to GIT and push them.
-  * Do a commit with a "Release <version>" line.
+
+  * In configure.ac set "my_isgit" to "no".
+
+  * Commit all changes to GIT with a message of "Release n.m.o."
+
   * Run "./autogen.sh --force"
     (--force is required for the svn magic in configure.ac and a good
     idea in any case)
+
   * Run "configure --enable-maintainer-mode".
+
   * Run "make distcheck".
+
   * Build and test the new tarball (best on a different machine).
+
   * Build and test the W32 version.
+
   * [2.x only] Using the final test build run a "make -C doc online".
+
   * Sign the tarball
+
   * Get the previous tarball and run "mkdiff gnupg".
     You might need to set a different signature key than mine.  mkdiff
     has an option for this.
-  * If you are satisfied with the result commit a tag for the release.
+
+  * If you are satisfied with the result commit a tag for the release
+    and push the changes.
+
   * Copy the files to the FTP server
+
   * Update the webpages - at least the file swdb.wml needs an update.
+
   * Add a new headline to NEWS.
-  * Bump "my_version" up and set "my_issvn" back to "yes" in configure.ac
-  * Write an announcement.  Update https://savannah.gnu.org/projects/gnupg .
+
+  * Bump "my_version" up and set "my_isgit" back to "yes" in configure.ac
+
+  * Write an announcement.
+
+  * Update https://savannah.gnu.org/projects/gnupg .
 
 
 

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

Summary of changes:
 README.maint |   45 +++++++++++++++++++++++++++++++++++----------
 1 files changed, 35 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
The GNU Privacy Guard
http://git.gnupg.org