- Let people know of a pending release, e.g. libcdio-devel@gnu.org;
  no major changes before release, please

- test on lots of platforms; sourceforge compile farm, for example

- "make distcheck" should work.

- Look for/fix/apply patches and outstanding bugs on Savannah.

- Go over Changelog and add NEWS. Update date of release.

- Remove "git" from configure.ac's release name. E.g.
    define(RELEASE_NUM, 93)
                        ^^
    define(PARANOIA_VERSION, 10.2)
    define(LIBCDIO_PARANOIA_VERSION_STR, $1+0.$2)
    define(RELEASE_NUM, 23)
    ...

- make doxygen documentation
  cd doc/doxygen; ./run_doxygen
     remove any errors.

- Make sure sources are current and checked in:
[    git pull

- autogen.sh && make && make check

  git commit -m"Get ready for release release-${LIBCDIO_PARANOIA_VERSION}"

- Tag release in git:
  git tag release-${LIBCDIO_PARANOIA_VERSION}
  git push --tags

- "make distcheck" one more time

- Get onto ftp.gnu.org. I use my perl program
   gnu-ftp-upload libcdio-paranoia ${LIBCDIO_PARANOIA_VERSION} libcdio

   Also gnupload from the automake distribution.
   /src/build/automake-1.12.4/lib/gnupload --to ftp.gnu.org:libcdio libcdio-paranoia-10.2+0.93.1.tar.gz  (Use "is" password)

- Update/Announce on Freshmeat:
   http://freshmeat.net/add-release/36670/
   (http://freshmeat.net/projects/libcdio/ "add release")

  The NEWS file is your friend.

- copy doxygen html to web pages:
  cd libcdio-www/doxygen
  rm *.html
  cp /src/external-vcs/github/libcdio-paranoia/doc/doxygen/html/*.html .
  cvs update .

    for each "U" html *except libcdio.html* that is put back, remove it
    with "rm" and then "cvs remove". For example,
    put in file /tmp/libcdio-remove.txt

       cvs remove `cat /tmp/libcdio-remove.txt`

    for each new "?" html add it. For example:
    put in file /tmp/libcdio-new.txt and run:
       cvs add `cat /tmp/libcdio-new.txt`


  cvs commit .

- Bump version in configure.ac and add "git". See place above in
  removal.
