Maliit/Making a Release

Revision as of 00:15, 21 June 2011

1. Update the NEWS file

• git commit message:

Changes: Update NEWS for version y.x

• NEWS template:

y.x
===

CHANGES SINCE x.z
* List changes

BUG FIXES
* Fixes: BMC#12345 ...

2. For framework, bump version numbers in its config.pri

• git commit message:

Changes: Bump version to y.x

• MALIIT_VERSION: package version
• MALIIT_INTERFACE_VERSION: ???
• MALIIT_PLUGINS_INTERFACE_VERSION: plugins version
• MALIIT_PLUGINS_QUICK_INTERFACE_VERSION: plugins version for Qt Quick

3. Create a git tag

$ git tag -s -m "Released version y.x - ${insertWittyReleaseNameHere}" y.x

4. Push to repos (including the newly created tag)

$ git push --tags origin HEAD:master

• Keep in mind that a git tag is tied to a specific commit id. If you rebase your branch, then the commit id's will most likely change, meaning that your git tag will point to an old commit id. You will have to delete the tag and create a new one, in that case.

5. Write the release notes and send them to the appropriate mailing lists.

6. Update the list of releases.