libcdio-osx/doc/how-to-make-a-release.txt

- 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.

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

- Remove "cvs" from configure.ac's release name. E.g.
    define(RELEASE_NUM, 23)
    define(LIBVCD_VERSION_STR, 0.7.$1cvs)
                                     ^^^
    ...

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

- Make sure sources are current and checked in:
    cvs update -dPA .
    cvs commit .

- autogen.sh && make && make check

- Tag release in CVS: 
   cvs log -h configure.ac
   cvs tag release_*0_79* .

- "make distcheck" one more time

- Get onto ftp.gnu.org. I use my perl program
   gnu-ftp-upload libcdio 0.*79*

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

  The NEWS file is your friend.

- copy doxygen html to web pages:
  cd libcdio-www/doxygen
  rm *.html
  cp ../../libcdio/doc/doxygen/html/*.html .
  cvs update . 
    for each "U" html *except libcdio.hmtl* put back remove it 
      with "rm" and "cvs remove"
    for each new "?" html add it
  cvs commit .

- copy libcdio manual to web page:
     cd libcdio-www
     (cd ../libcdio/doc && make libcdio.html)
     cp ../libcdio/doc/libcdio.html .
     cvs commit libcdio.html

- Remove old cvs versions 

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