opendev/gerrit
Code Issues Proposed changes

dev-release-deploy-config: Expand instructions for PGP key generation

Browse Source 
- Recommend publishing the public key to Ubuntu server, as this is
  the server that we mention on the home page.

- Add an instruction to add an entry for the key on the homepage.

Change-Id: I1dfd47d8da2c00fa01405d874b3c2adec5a2d5fd
This commit is contained in:
David Pursehouse
2017-06-30 13:26:44 +09:00
parent 5420f8b5fc
commit 0d7746b742
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -38,15 +38,21 @@ permission by commenting on the same issue.
* Generate and publish a PGP key * 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.
+
Generate and publish a PGP key as described in Generate and publish a PGP key as described in
link:http://central.sonatype.org/pages/working-with-pgp-signatures.html[ link:http://central.sonatype.org/pages/working-with-pgp-signatures.html[
Working with PGP Signatures]. Working with PGP Signatures]. In addition to the keyserver mentioned
there it is recommended to also publish the key to the
link:https://keyserver.ubuntu.com/[Ubuntu key server].
+ +
Please be aware that after publishing your public key it may take a Please be aware that after publishing your public key it may take a
while until it is visible to the Sonatype server. while until it is visible to the Sonatype server.
+ +
The PGP key is needed to be able to sign the artifacts before the Add an entry for the public key in the
upload to Maven Central. link:https://gerrit.googlesource.com/homepage/+/md-pages/releases/public-keys.md[key list]
on the homepage.
+ +
The PGP passphrase can be put in `~/.m2/settings.xml`: The PGP passphrase can be put in `~/.m2/settings.xml`:
+ +