opendev/gerrit
Code Issues Proposed changes

dev-release: Add step to sign the announcement mail

Browse Source 
At the same time, remove redundant bullet points from the section.

Change-Id: I67ebc1da54a97b0b5e985d9d54f863e037afd4b4
This commit is contained in:
David Pursehouse 2017-06-30 13:37:11 +09:00
parent 0d7746b742
commit b3f1debc96
2 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/dev-release-deploy-config.txt
View File

@ -39,7 +39,7 @@ permission by commenting on the same issue.
* Generate and publish a PGP key
+
A PGP key is needed to be able to sign the release artifacts before
the upload to Maven Central.
the upload to Maven Central, and to sign the release announcement email.
+
Generate and publish a PGP key as described in
link:http://central.sonatype.org/pages/working-with-pgp-signatures.html[

14
Documentation/dev-release.txt
View File

@ -326,12 +326,14 @@ because `Status=Submitted` is considered a closed issue.
[[announce]]
==== Announce on Mailing List
* Send an email to the mailing list to announce the release, 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.
Send an email, signed with the same PGP key used to sign the release
artifacts, to the mailing list to announce the release.
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