Release Guide

This guide describes the process of doing an official release of Mesos.


  1. Ensure that you have a GPG key or generate a new one, e.g., using gpg --gen-key.

  2. Add your GPG public key to the Apache Mesos dist repository in the KEYS file.

    • Fetch the svn repository:
      svn co

    • Append your public key using one of methods described in KEYS, e.g.,
      (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS.

    • Push the commit:
      svn ci

  3. Submit your GPG public key to a keyserver, e.g., MIT PGP Public Key Server.

  4. Add your GPG fingerprint to your Apache account.

  5. Create a Maven settings file (~/.m2/settings.xml) for the Apache servers where you must copy your encrypted Apache password which you can get from running mvn --encrypt-password (NOTE: you may need to first generate a master password.

          <username>APACHE USERNAME</username>
          <password>APACHE ENCRYPTED PASSWORD</password>
          <username>APACHE USERNAME</username>
          <password>APACHE ENCRYPTED PASSWORD</password>
  6. Use gpg-agent to avoid typing your passphrase repeatedly.


  1. Go to Apache Jira and make sure that the CHANGELOG for the release version is up to date.

    NOTE: You should move all Unresolved tickets marked with Fix Version or Target Version as the release version to the next release version.

    PROTIP: Use a JIRA dashboard (example) to track the progress of targeted issues as the release date approaches.

    PROTIP: Use bulk edit option in JIRA to move the tickets and make sure to uncheck the option that emails everyone about the move.

  2. Update and commit the CHANGELOG for the release. For major releases we like to call out any major features, API changes, or deprecations.

    NOTE: You should use JIRA to generate the CHANGELOG for you. Click on the release version in JIRA and click on the Release Notes. Make sure to configure the release notes in text format.

    NOTE: The JIRA Release Notes will list only tickets with Fix Version set to that version. You should check for any Resolved tickets that have Target Version set but not Fix Version. Also check for any Unresolved or Duplicate/Invalid tickets that incorrectly set the Fix Version.

  3. If not already done, update and commit for the release.

  4. Update and commit docs/ to reflect the current state of the master, slave, and configure flags.

  5. Update and commit docs/ with instructions about how to upgrade a live cluster from the previous release version to this release version.

  6. If this is a major release, please ensure that user documentation has been added for any new features.

Tagging the release candidate

  1. Ensure that you can build and pass all the tests.

    $ sudo make -j3 distcheck
  2. First tag the required SHA locally.

    $ git tag <X.Y.Z-rcR>

    NOTE: X.Y.Z is based on semantic versioning scheme. R is release candidate version that starts with 1.

  3. Tag the release externally and deploy the corresponding JAR to the Apache maven repository. It is recommended to use the support/ script to accomplish this.

    $ ./support/ X.Y.Z R

    NOTE: This script assumes that you have the requisite permissions to deploy the JAR. For instructions on how to set it up, please refer to src/java/MESOS-MAVEN-README.

    NOTE: gnu-sed (Linux) requires -i'' instead of the -i '' (space-separated) that default OSX uses. You may need to modify your local copy of for it to complete successfully.

  4. It is not uncommon to release multiple release candidates, with increasing release candidate version, if there are bugs found.

  5. Update to the next Mesos version in change AC_INIT([mesos], [X.Y.Z])) and commit.

Voting the release candidate

  1. Once a release candidate is deemed worthy to be officially released you should call a vote on the (and optionally mailing list.

  2. It is recommended to use the support/ script to vote the release candidate.

    $ ./support/ X.Y.Z R
  3. The release script also spits out an email template that you could use to send the vote email.

    NOTE: The date -v+3d command does not work on some platforms (e.g. Ubuntu), so you may need to fill in the vote end date manually. The vote should last for 3 business days instead of 3 calendar days anyway. Sometimes we prefer a weeklong vote, to allow more time for integration testing.

Preparing a new release candidate

  1. If the vote does not pass (any -1s or showstopper bugs), track the issues as new JIRAs for the release.

  2. When all known issues are resolved, update the CHANGELOG with the newly fixed JIRAs.

  3. Once all patches are committed to master, cherry-pick them on top of the previous release candidate tag. This is the same process used for point releases (e.g. 0.22.1) as well.

    $ git checkout X.Y.Z-rcR
    $ git cherry-pick abcdefgh...
  4. Now go back up to the "Tagging the release candidate" section and repeat.

Releasing the release candidate

  1. You should only release an official version if the vote passes with at least 3 +1 binding votes and no -1 votes. For more information, please refer to Apache release guidelines.

  2. It is recommended to use support/ script to release the candidate.

    $ ./support/ X.Y.Z R
  3. The release script also spits out an email template that you could use to notify the mailing lists about the result of the vote and the release.

    NOTE: Make sure you fill the email template with the names of binding voters.

Updating the website

  1. After a successful release, please update the website pointing to the new release. See our website README and the general Apache project website guide for details on how to build and publish the website.

    $ svn co mesos-site
  2. Write a blog post announcing the new release and its features and major bug fixes.

  3. Update the Getting Started guide to use the latest release link.

Remove old releases from svn

Per the guidelines when to archive, we should only keep the latest release in each version under development.

  1. Checkout the mesos distribution folder: svn co

  2. Remove all minor versions that are no longer under development and commit the change.

Set the release date

  1. Find the released Mesos version on, and "release" it with the correct release date.

Update external tooling

Upload the mesos.interface package to PyPi.

  1. Create/use a PyPi account with access to the mesos.interface submit form. You may need to ask a current package owner to add you as an owner/maintainer.
  2. Setup your ~/.pypirc with your PyPi username and password.
  3. After a successful Mesos make (any architecture), cd to build/src/python/interface.
  4. Run python register to register this package.
  5. Run python bdist_egg upload to upload the egg for this package.

Update the Mesos Homebrew package.

  1. Update the Homebrew formula for Mesos and test.
  2. Submit a PR to the Homebrew repo.
  3. Once accepted, verify that brew install mesos works.