From 5051a512141f642f90f53f2749ddd8cc815226e4 Mon Sep 17 00:00:00 2001 From: Marti Bolivar Date: Fri, 7 Oct 2011 15:21:29 -0400 Subject: README: More on how to maintain releases. Signed-off-by: Marti Bolivar --- README | 29 ++++++++++++++++++++++++++--- 1 file changed, 26 insertions(+), 3 deletions(-) diff --git a/README b/README index 2fe5092..4cdf66f 100644 --- a/README +++ b/README @@ -310,11 +310,34 @@ It needs to be updated RIGHT AWAY, you say? Here's what you do: - Make your changes. -- Rebuild the docs (see the last two steps in "Cutting the Release"). +- Rebuild the docs (see the last two steps in "Cutting the Release") + and look at the changed pages. -- If your changes need to happen on the master branch, make them +- If your changes also need to happen on the master branch, make them appropriately. + Advice: git cherry-pick is your friend. Let's say you're on branch + "vX.Y.Z-maintenance", and you want to get commit C onto master: + + o---C vX.Y.Z-maintenance + / + -o---o---o---o master + + The recipe is: + + $ git checkout master + $ git cherry-pick C + + Which (if there are no conflicts) will result in: + + o---C vX.Y.Z-maintenance + / + -o---o---o---o---C' master + + Where C' performs the same changes as C. + - Push your fixes to GitHub. -- Distribute the updated docs. +- Distribute the updated docs. These are world-visible here: + + http://static.leaflabs.com/pub/leaflabs/maple-docs/ -- cgit v1.2.3