Release Checklist

This is an attempt to enumerate what needs to be done to cut a new release.

What to do before release time

• Freeze strings and attempt to get translators to update their respective languages
• Perform a pass through the bug tracker to see if there are any release blocker issues
• Test daily builds on as many targets as possible. Even just a basic boot/smoke test is better than nothing
• Consider producing updated bootloader binaries, if added features warrant it
• Update manuals -- Additional targets, updated screenshots and keymaps, etc
• Ensure wiki reflects reality (MajorChanges, TargetStatus, WebHome [ie target status] etc etc..)
• Ensure copyright year in manual/intro/main.tex is current
• Ensure docs/PLUGIN_API is current (see utils/rockbox_api)

What to do at release time

• Make sure you are working with a pristine, up-to-date git tree
• Update tools/builds.pm and fill in the release specifics and any other changes (stable/manual/sim promotion, etc -- Look for 'Remove' in comments!)
• Create a signed git tag (see https://www.rockbox.org/wiki/UsingGit#Tagging) and don't forget to git push --tags!
• Run scripts under tools/release/* to create firmware, manuals, voice files, and source tarball. This will likely take some time!
• Upload all of the build artefacts to the download site under /releases
• Update www/tools/buildall_voices.sh to include full list of voices for new release
• Create release notes page on the wiki and update MajorChanges for new release/date
• Add the release number (if necessary) to flyspray, make it 'current' and demote previous version to 'past'. Create a new 'future' entry for the next release
• Update www site's update_front.sh to include the new git tag
• Update themesite checkwps binaries (see private/checkwps/release/update.sh) and force a checkwps run
• Manually run tools/build-info to create new build-info.release and run .scripts/mkbuildinfo.sh to update the global build-info (normally done after every dev build round and nightly)
• Make sure rbutil does the right thing with the new release info
• Draft a "press release" with appropriate/correct "facts"
• Update main web site (index.t, history.t) with new release info
• Send announcement to mailing lists and forum
• Update banner on IRC channel