Module: Mesa Branch: master Commit: f1890b7ad85b74bd92c858919a304dce8f7aae10 URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=f1890b7ad85b74bd92c858919a304dce8f7aae10
Author: Dylan Baker <dy...@pnwbakers.com> Date: Mon Oct 28 08:48:44 2019 -0700 docs: update releasing to cover updated post_version.py Reviewed-by: Eric Engestrom <eric.engest...@intel.com> Reviewed-by: Juan A. Suarez <jasua...@igalia.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2505> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2505> --- docs/releasing.html | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/releasing.html b/docs/releasing.html index e5a453799bb..15ec38a3771 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 </pre> -<p>Then run the <code>./bin/post_verison.py X.Y.Z</code>, 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: +<p>Then run the <pre>./bin/post_verison.py X.Y.Z</pre>, 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: </p> <pre> -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 </pre> _______________________________________________ mesa-commit mailing list mesa-commit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-commit
