Release Process/Release
At the end of the stabilization phases, the final release candidate is agreed as good and becomes the final release. This page outlines the steps needed to wrap-up the release.
Finalize release notes
At this point, the release notes should be checked and published as final with any {{draft}} tag removed.
Update download.laptop.org
The http://download.laptop.org index.html front page should be updated (manually) and the build moved from 'candidate' to 'official' in the files hierarchy.
Finalize frozen repositories
The Frozen repositories used in the release should now be finalized (see Frozen_repositories#Finalizing_a_release).
Make build system release
For olpc-os-builder:
- The version number should be incremented appropriately
- The suggested_oob_version field in the build configuration should be set to this version
- After committing, a git tag (with that version number) should be made and pushed
- A new tarball should be released
- The new version should be packaged in Fedora
Update release page
The release page (e.g. 11.2.0) should then be updated.
- The status property should be set to "released"
- The following properties should be set appropriately: Property:Build number, Property:Build system, Property:Build system version, Property:Build platform, Property:Download URL, Property:Firmware
Announce the release
Send a mail to the devel mailing list announcing the availability of the release.
Send the build to the factory
Quanta (the laptop manufacturer) should be informed of the availability of the new build. They will install it on new laptops where the deployment has not provided a custom software image.
To do this, ask a member of OLPC staff to inform Quanta of the new release by sending a mail to the production mailing list.
Quanta will likely do a week or two of their own QA before the new software build hits production.