Repository: mesos
Updated Branches:
  refs/heads/master 54339eb0e -> f7d91ba2f


Updated release guide to recommend regenerating endpoint help.

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


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

Branch: refs/heads/master
Commit: f7d91ba2f33086d3d8be8b3011aaa28d1932afdb
Parents: 54339eb
Author: Neil Conway <neil.con...@gmail.com>
Authored: Wed May 18 15:30:11 2016 +0200
Committer: Alexander Rukletsov <al...@apache.org>
Committed: Wed May 18 15:30:11 2016 +0200

----------------------------------------------------------------------
 docs/release-guide.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/f7d91ba2/docs/release-guide.md
----------------------------------------------------------------------
diff --git a/docs/release-guide.md b/docs/release-guide.md
index d0f228f..6878219 100644
--- a/docs/release-guide.md
+++ b/docs/release-guide.md
@@ -81,16 +81,18 @@ This guide describes the process of doing an official 
release of Mesos.
 
 3. If not already done, update and commit `configure.ac` for the release.
 
-4. Update and commit `docs/configuration.md` to reflect the current state of
+4. Run `support/generate-endpoint-help.py` and commit any resulting changes.
+
+5. Update and commit `docs/configuration.md` to reflect the current state of
    the master, agent, and configure flags.
 
-5. Update and commit `docs/upgrades.md` with instructions about how to upgrade
+6. Update and commit `docs/upgrades.md` 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
+7. If this is a major release, please ensure that user documentation has been
    added for any new features.
 
-7. Make sure that for any updates of the API, specifically the scheduler API, 
the public mesos protobuf definitions are part of both, `include/mesos` as well 
as `include/mesos/v1`. NOTE: This might actually demand code updates if any 
omissions were identified.
+8. Make sure that for any updates of the API, specifically the scheduler API, 
the public mesos protobuf definitions are part of both, `include/mesos` as well 
as `include/mesos/v1`. NOTE: This might actually demand code updates if any 
omissions were identified.
 
 ## Tagging the release candidate
 

Reply via email to