Page History

...

You will be prompted for a commit message, and (probably) the gpg passphrase. If you need to specify a specific signing key, you can configure that in git (signkey) or specify it with the -u option to git tag.

CHANGES

...

, STATUS, and docs/conf.py files

Before cutting a release, please make sure the CHANGES and STATUS files are up to date. In particular, make sure that the CHANGES file on trunk is in sync with the release branches (currently only 2.0.x). The CHANGES should include major feature changes or bug fixes for a release.

Versioning is controlled in the configure.ac file, it should be the only file necessary to be modified to change the release version number.

The documentation version is set by docs/conf.py.  Make sure to set the new version on master and make sure the release version is correct.

RAT reports

The Release Audit Tool Tool reports are automatically generated on both trunk and all active release branches. The current reports are

...