Notes for the GnuPG maintainer  (SVN only)
           ============================================

Here are some notes on how to maintain GnuPG.


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.
  * Run "make update-po".
  * Write NEWS entries and set the release date in NEWS.
  * In configure.ac set "my_issvn" to "no".
  * Commit all changes to the SVN.
  * Update the SVN then (to sync the release number of all files).
  * Run "./autogen.sh --force"
    (--force is required for the svn magic in configure.ac and a good
    idea in any case)
  * Run "make distcheck"
  * Build and test the new tarball (best on a different machine).
  * [1.4 only] Build and test the W32 vesion.
  * 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 satisied with the result tag the release.  Use "svn
    info" to get the current URL and use an svn cp command similar to
    "svn cp svn+ssh://host/gnupg/trunk  svn+ssh://host/gnupg/tags/2.n.m"
    (for 1.4 you should see "branches/STABLE-BRANCH-1-4" instead of "trunk",
     however tags are all below tags).
  * 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.