Mailing-List: contact commits-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: bmahler@apache.org
To: commits@mesos.apache.org
Message-Id: <f2b3426655064ff0a7d7b0c48d30efd1@git.apache.org>
Subject: mesos git commit: Updated release guide to include running the
 benchmarks.
Date: Thu, 28 Jan 2016 00:20:14 +0000 (UTC)

Repository: mesos
Updated Branches:
  refs/heads/master 65166763e -> 3558d5951


Updated release guide to include running the benchmarks.

Review: https://reviews.apache.org/r/42881


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/3558d595
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/3558d595
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/3558d595

Branch: refs/heads/master
Commit: 3558d5951525fa0a24f8eae0b4f89105eca1a67e
Parents: 6516676
Author: Benjamin Mahler <benjamin.mahler@gmail.com>
Authored: Wed Jan 27 16:06:39 2016 -0800
Committer: Benjamin Mahler <benjamin.mahler@gmail.com>
Committed: Wed Jan 27 16:06:53 2016 -0800

----------------------------------------------------------------------
 docs/release-guide.md | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/3558d595/docs/release-guide.md
----------------------------------------------------------------------
diff --git a/docs/release-guide.md b/docs/release-guide.md
index 7c9ee14..3a6b7d9 100644
--- a/docs/release-guide.md
+++ b/docs/release-guide.md
@@ -95,16 +95,20 @@ This guide describes the process of doing an official release of Mesos.
 
 1. Ensure that you can build and pass all the tests.
 
-        $ sudo make -j3 distcheck
+        $ sudo make -j<cores> distcheck
 
-2. First tag the required SHA locally.
+2. Run the benchmarks and compare with the previous release for any performance regressions:
+
+        $ make bench -j<cores> GTEST_FILTER="*BENCHMARK*"
+
+3. First tag the required SHA locally.
 
         $ git tag <X.Y.Z-rcR>
 
     > NOTE: `X.Y.Z` is based on [semantic versioning](http://semver.org/) 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.
+4. Tag the release externally and deploy the corresponding JAR to the Apache maven repository.
    It is recommended to use the `support/tag.sh` script to accomplish this.
 
         $ ./support/tag.sh X.Y.Z R
@@ -115,10 +119,10 @@ This guide describes the process of doing an official release of Mesos.
     > 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 tag.sh for it to complete successfully.
 
-4. It is not uncommon to release multiple release candidates, with increasing release candidate
+5. 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 `configure.ac`: change `AC_INIT([mesos], [X.Y.Z]))`, as well as in `CMakeLists.txt`: change `set(MESOS_MAJOR_VERSION X)`, `set(MESOS_MINOR_VERSION Y)`, `set(MESOS_PATCH_VERSION Z)` and then commit.
+6. Update to the *next* Mesos version in `configure.ac`: change `AC_INIT([mesos], [X.Y.Z]))`, as well as in `CMakeLists.txt`: change `set(MESOS_MAJOR_VERSION X)`, `set(MESOS_MINOR_VERSION Y)`, `set(MESOS_PATCH_VERSION Z)` and then commit.
 
 ## Voting the release candidate