The release notes are completely generated by the
``bin/gen_release_notes.py`` script. Simply run this script **before**
bumping the version. You'll need to come back to this file once the
-tarball is generated to add its ``sha256sum``.
+tarball is generated to add its SHA256 checksum.
Increment the version contained in the file ``VERSION`` at Mesa's top-level,
then commit this change and **push the branch** (if you forget to do
<release-maintainers-keys.asc>`__.
-Add the sha256sums to the release notes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Add the SHA256 checksums to the release notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Edit ``docs/relnotes/X.Y.Z.rst`` to add the ``sha256sum`` as available in the
-``mesa-X.Y.Z.announce`` template. Commit this change.
+Edit ``docs/relnotes/X.Y.Z.rst`` to add the SHA256 checksums as available
+in the ``mesa-X.Y.Z.announce`` template. Commit this change.
Don't forget to push the commits to both the ``staging/X.Y`` branch and
the ``X.Y`` branch: