From f1890b7ad85b74bd92c858919a304dce8f7aae10 Mon Sep 17 00:00:00 2001 From: Dylan Baker Date: Mon, 28 Oct 2019 08:48:44 -0700 Subject: [PATCH] docs: update releasing to cover updated post_version.py Reviewed-by: Eric Engestrom Reviewed-by: Juan A. Suarez Tested-by: Marge Bot Part-of: --- docs/releasing.html | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/releasing.html b/docs/releasing.html index e5a4537..15ec38a 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -381,15 +381,14 @@ git cherry-pick -x X.Y~1 git cherry-pick -x X.Y -

Then run the ./bin/post_verison.py X.Y.Z, where X.Y.Z is the -version you just made. This will updated docs/relnotes.html and -docs/index.html. Remove the new release from docs/release-calendar.html. Then -commit and push: +

Then run the 

./bin/post_verison.py X.Y.Z
, where X.Y.Z is the +version you just made. This will updated docs/relnotes.html, +docs/index.html, and docs/release-calendar.html. It will then generate +a git commit automatically. Check that everything looks correct and push: 

-git commit -as -m "docs: update calendar, add news item and link release notes for X.Y.Z"
-git push origin master X.Y
+	git push origin master X.Y
-- 2.7.4