That's how we do a release:

1.  For a patch level release skip 1. and start with 2.

    For a new major or minor release create a release branch based on
    the version number for the new release.
    
    If the next release will have the version 0.1.0 create a 0.1.x
    branch from trunk with the commit message: "created 0.1.x release
    branch."
             
2.  Increase the version number on trunk in sublib/version.in.h and
    configure.ac. In case of the 0.1.0 example increase it to 0.2.0.
    Commit.

    or
        
    In case of patch level release increase the patch level version
    number on the release branch in sublib/version.in.h and
    configure.ac.
    Commit.    

3.  Add a new entry to the CHANGES file on trunk for the new release.
    In our example 0.1.0 or 0.1.n in case of a patch release. Fill up
    the CHANGES entry.
    Commit.

4.  Update website (index.html/history.html) on trunk.
    Do not commit! See the last few steps.

5.  Create a working copy from the release branch. In our example from
    branches/0.1.x.

6.  In case of a patch release merge fixes and changes from trunk.
    Commit.

7.  Merge the CHANGES file into the release branch. In our example the
    0.1.x release branch.
    Commit.

8.  Create a tag from the release branch with the commit message:
    "created 0.1.0 release tag."
             
9.  Switch the branch working copy to the created tag. Run gen_version.h
    -n (maybe add special build text).

10. create source archive (tgz) of the tag working copy.

    make sdist

11. build tag working copy on Windows and create win32 installer.

    needed files:
    
    locale   
    icons
    iconv
    libdb42.dll
    libeay32.dll
    ssleay32.dll
    qt-mtnc321.dll
    msvcr80.dll
    msvcp80.dll
    dbghelp.dll

12. build tag working copy on MacOSX and create disk image.

    make bundle
    make image
    
13. Increase the version number in version.in.h on the release branch.
    Commit.
    
    In the 0.1.0 example increase the version number on the 0.1.x branch
    to 0.1.1. 

14. Upload srczip and tgz, MacOSX disk image and the win32 installer.

15. Commit updated Website on trunk.
    -> goes Online.

16. Add project announcement at subcommander.tigris.org and send release
    email to dev/announce mailing lists.

    Done, finally !!!
