From Askmonty.org

Procedures for doing a MariaDB release

This page is to document the release process for MariaDB.

Currently there is not much content here, TODO.

The procedure for 5.1 releases:

1. Commit fixes into 5.1-release tree until Buildbot looks OK
2. Monty Program tags the 5.1-release tree with a release tag (e.g. tag:mariadb-5.1.39-beta for the 5.1.39 release, see below for sample command line)
3. A notification is sent to the following that the tag has been created:
   1. Daniel (release note author)
4. Monty Program notifies the following of the tag and that the tree is ready for release:
   1. OurDelta (mail+IRC)
   2. The Docs team (docs 'at' askmonty 'dot' org)
   3. The community team (community 'at' askmonty 'dot' org)
   4. Ethan
5. OurDelta builds packages and informs the Docs team of the filenames and md5sums
6. Currently Sergey Petrunya handles building Windows zip binaries.
7. Packages get uploaded to mirrors
8. 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. Remember to route all links to mirrors and repositories via the download tracker: http://buildbot.askmonty.org/downloads/r/<target>
   5. A page including the template is also created at this time and a link to it is placed in the "Previous Releases" section. 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.
9. The Docs team fills in, edits, and finishes the release notes and changelog pages and removes the Template:MariaDB Unreleased banner about the information on the page being about an unreleased version
10. 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:MariaDB 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: {{MariaDB Unreleased}}
11. The Docs team preps updates to other documentation as necessary
12. 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
13. Monty Program announces the release on the News page and via blogs and other methods

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

Obtaining info for release notes

A raw log of all changes can be obtained from bzr as follows:

 bzr branch --no-tree -rtag:mariadb-5.1.38-beta mariadb-5.1 mariadb-5.1.38-beta
 bzr branch --no-tree -rtag:mariadb-5.1.39-beta mariadb-5.1 mariadb-5.1.39-beta
 cd mariadb-5.1.39-beta/
 bzr missing --line --include-merges ../mariadb-5.1.38-beta > /tmp/short.txt
 bzr missing --include-merges ../mariadb-5.1.38-beta > /tmp/long.txt

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