Release Process

Procedures for doing a MariaDB release

This page documents the release process for MariaDB.

Procedure for 5.1 releases

1. Commit fixes into 5.1-release tree until Buildbot looks OK
2. The Release Coordinator adds a release tag to the release tree (e.g. tag:mariadb-5.1.39-beta for the 5.1.39 release, see note 1 below for sample command line)
3. The Release Coordinator notifies the following of the tag and that the tree is ready for release:
   1. The Maria Docs team (maria-docs [at] lists (dot) launchpad (dot) net)
   2. OurDelta (mail+IRC)
   3. The community team (community [at] askmonty (dot) org)
   4. Ethan
4. The Builbot buildslaves build packages and Kristian copies the packages to hasky and informs the Docs team when they have been copied over
5. Ping Bo when the source tarball is ready, for manual Windows build
6. Kristian uploads files to launchpad
7. Daniel creates md5sums of all files (see note 2 below)
8. Packages get uploaded to mirrors (this happens automatically as soon as the files are uploaded to hasky)
9. The Docs team preps a replacement MariaDB Download page
   1. The majority of the download page is a download page template specific to the new version of MariaDB
   2. The previous download page template is used as the source template for the new download page template
   3. Sections for various distros (Ubuntu, Debian, CentOS, Windows) should not be hidden if there are not updated packages for them right away, instead a "Coming soon..." placeholder should be used and a link to the previous release with existing packages can be added.
   4. All links to mirrors and repositories are routed through the download tracker: http://askmonty.org/downloads/r/<target>
      • The preferred method for creating mirror links is to use the mirrors template. See the template for instructions on how to use it.
   5. A page including the template is also created at this time and a link to it is placed in the Download:Releases template. The text marking the current release should be moved next to this link.
      • Name the links and pages according to the naming convention on the page.
10. The Docs team fills in, edits, and finishes the release notes and changelog pages and removes the {{unreleased}} template about the information on the page being about an unreleased version
11. The Docs team creates release notes and changelog pages for the next release (so that the developers can fill them in as they work on the release)
    • The Template:unreleased banner should be placed on these pages to let users know that the information on the page is about an unreleased version. The wiki syntax for including the template is: {{unreleased}}
12. The Docs team preps updates to other documentation as necessary
13. Once all packages have been mirrored, the Docs team swaps out the MariaDB Download page (archiving the old one) and activates any other documentation changes/additions
14. The Docs team updates the release RSS feed
15. The community team announces the release on the News page, the announce mailing list, and via blogs and other methods

Notes

1. Tagging releases: Here is an example bzr command line to make the tag:

bzr tag --directory lp:~maria-captains/maria/5.1-release mariadb-5.1.41-rc

1. Creating md5sums: Here are the commands I (Daniel) use to create the md5sums of a release:

cd /path/to/dir/with/releases/
release='mariadb-5.2.1-beta'
for dir in $(find ${PWD}/${release} -type d); do echo; echo ${dir};cd ${dir};md5sum *;echo;echo;done

1. Obtaining info for Changelog and Release Notes: A raw log of all changes can be obtained from bzr as follows:

sourcedir="5.1"
oldrelease="mariadb-5.1.44b"
newrelease="mariadb-5.1.47"
bzr branch --no-tree -rtag:${oldrelease} ${sourcedir} ${oldrelease}
bzr branch --no-tree -rtag:${newrelease} ${sourcedir} ${newrelease}
cd ${newrelease}/
bzr missing --line --include-merges ../${oldrelease} > /tmp/short.txt
bzr missing --include-merges ../${oldrelease} > /tmp/long.txt

It is then a manual process to read through this and convert it into some kind of human-readable release notes...