Slightly improve instructions for updating docs/release.md

It makes more sense to update it manually once and then run the script
rather than partially updating it manually first, then updating it again
and then running the script.
This commit is contained in:
Vadim Zeitlin 2018-12-09 16:55:42 +01:00
parent d06720d4c9
commit edbee125f9

View File

@ -51,7 +51,7 @@ and then run it using the new DLLs.
automatically, but please also review and update the contents of the README
and announcement text.
* Update `docs/readme.txt`: version needs to be changed, content updated.
* Update `docs/release.md`: the release sha1sums should be set to zeroes.
* Update `docs/release.md`: also version and reset SHA-1 sums to zeroes.
* Put a date on the release line in `docs/changes.txt`.
* Update the date in the manual (`docs/doxygen/mainpages/manual.h`).
* Update the release announcement post in `docs/publicity/announce.txt`.
@ -91,10 +91,9 @@ ensure you have the appropriate tag or commit checked out.
and copy/move it to the same directory.
5. Update the version in `docs/release.md` (typically just a global search and
replace) and run `./build/tools/post-release.sh` to update the sha1sums in
it, then commit the changes. Notice that when making an RC, the version must
be explicitly specified on this script command line.
5. Run `./build/tools/post-release.sh` to update the SHA-1 sums in
`docs/release.md`, then commit the changes. Notice that when making an RC,
the version must be explicitly specified on this script command line.
## Uploading