Release Checklist

CEGUI

This page is mainly for the CEGUI team and serves as a checklist to avoid forgetting steps when making a CEGUI release.

• First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.
• Bump release version in CMakeLists.txt
• Bump ABI version in CMakeLists.txt
• Add change log entries from https://bitbucket.org/cegui/cegui/issues?milestone=0.8.4&status=resolved (change the version in the link) to doc/doxygen/changelog.dox
• Regenerate generated code/other files (i.e regen bindings etc)
• Create mercurial tag for release
• Make source packages.
• Build docs.
• Make docs packages.
• Upload!
• Make sure the new release is listed as the latest release on sourceforge, you can do this by clicking the "i" icon next to the file and selecting all operating systems --> SAVE (takes 3 mins to be updated)
• For 0.8.5 Release announce in the docs and in the Release news that this requires CMAke 2.8.11 minimum <-- what happened to this?
• Create a release on the drupal page - http://cegui.org.uk/node/add/release
• Make sure N+1 version is in bitbucket issue-tracker or add it - also make it the default (bitbucket repo -> Settings -> Issues -> Versions)
• Generate docs and upload to static.cegui.org.uk, see http://bitbucket.org/cegui/docs-builder
• Update the server's htaccess in the static API docs folder to redirect to the latest minor version
• Post to twitter
• Post to google+

CEED

• First check that the local repo is completely up-to-date and check that no unversioned files or uncommited changes are existing.
• Bump release version in ceed/version.py
• Make source packages.
• Build docs.
• Upload!
• Create a release on the drupal page - http://cegui.org.uk/node/add/release
• Make sure N+1 version is in bitbucket issue-tracker or add it