Difference between revisions of "Release Checklist"
From CEGUI Wiki - Crazy Eddie's GUI System (Open Source)
Line 6: | Line 6: | ||
* Bump release version in CMakeLists.txt | * Bump release version in CMakeLists.txt | ||
* Bump ABI version in CMakeLists.txt | * Bump ABI version in CMakeLists.txt | ||
− | * Add change log entries from | + | * 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) | * Regenerate generated code/other files (i.e regen bindings etc) | ||
* Create mercurial tag for release | * Create mercurial tag for release |
Revision as of 18:36, 26 April 2015
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
- 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
- Generate docs and upload to static.cegui.org.uk, see http://bitbucket.org/cegui/docs-builder
- Post to twitter
- Post to google+
CEED
TODO