docs: update releasing to cover updated post_version.py

Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
Reviewed-by: Juan A. Suarez <jasuarez@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>
This commit is contained in:
Dylan Baker
2019-10-28 08:48:44 -07:00
parent 5cdaa06221
commit f1890b7ad8

View File

@@ -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>