opendev/gerrit
Code Issues Proposed changes

dev-release: Document usage of release-announcement.py

Browse Source 
Change-Id: I0e658c62d4bdc5f40c0de37cf68c82d76b66cd01
This commit is contained in:
David Pursehouse
2017-07-19 11:06:52 +09:00
parent 397b0f69f0
commit d15e43688e
1 changed files with 10 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
Documentation/dev-release.txt
View File

@@ -326,19 +326,17 @@ because `Status=Submitted` is considered a closed issue.
[[announce]]
==== Announce on Mailing List
Send an email, signed with the same PGP key used to sign the release
artifacts, to the mailing list to announce the release.
Send an email to the mailing list to announce the release. The content of the
announcement email is generated with the `release-announcement.py` which
automatically includes all the necessary links, hash values, and wraps the
text in a PGP signature.
Consider including some or all of the following in the email:
* A link to the release and the release notes
* A link to the docs
* Describe the type of release (stable, bug fix, RC)
* Hash values (SHA1, SHA256, MD5) for the release WAR file.
+
The SHA1 and MD5 can be taken from the artifact page on Sonatype. The
SHA256 can be generated with
`openssl sha -sha256 bazel-bin/release.war` or an equivalent
command.
For details refer to the documentation in the script's header, and/or the
help text:
----
./tools/release-announcement.py --help
----
[[increase-version]]
=== Increase Gerrit Version for Current Development