Commit the auto-generated doc changes to current branch ("Regenerated docs for X.Y.Z release.")

update CHANGES.txt (should already be up to date)

update Announce.txt (not for checkpoints): add section for this release, important user-visible changes only. This is really long since it also has old releases. Is it useful?

update RELEASE.txt: this gets its content replaced for each release. New functionality, deprecated functionality, changed functionality, and fixes. Get this from CHANGES.txt. Add new contributors to list at end.

edit debian/changelog. Be careful of formatting here, it gets machine-parsed.

NOTE: I think Announce and Release are backwards; Release should be complete release notes for all versions (latest at top) and Announce should be a short blurb of just this release. FIXME!

Commit this to the current branch (normally default branch in hg, unless this release is coming off a branch).

You should now have the following in build/dist:
scons-$VERSION-1.noarch.rpm
scons-$VERSION-1.src.rpm
scons-$VERSION.linux-x86_64.tar.gz
scons-$VERSION.linux-x86_64.zip
scons-$VERSION.tar.gz
scons-$VERSION.win32.exe
scons-$VERSION.zip
scons-doc-$VERSION.tar.gz
scons-local-$VERSION.tar.gz
scons-local-$VERSION.zip
scons-src-$VERSION.tar.gz
scons-src-$VERSION.zip

The .linux-x86_64 ones are not needed and may be deleted; the others all get uploaded to SF.

Upload Software and Doc

There is now a shell script to do this: bin/upload-release-files.sh X.Y.Z mysfusername as long as SourceForge and scons.org have your ssh pub key and you're using SSH Agent Forwarding.

It uploads all the packages to SF, uploads the doc to scons.org, unpacks it, and updates the doc symlinks.
** You will be prompted for your password numerous times.

You may still have to tell SF that the new release dirs exist in its File Manager (it's a bit buggy).