TINKERPOP-1433 CTR: added release manager key setup docs.
Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/aa262d6b Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/aa262d6b Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/aa262d6b Branch: refs/heads/TINKERPOP-1602 Commit: aa262d6bdfc6177b24bcced4346e1cc2f2cb505f Parents: fe5f557 Author: Ted Wilmes <twil...@gmail.com> Authored: Mon Jan 23 16:47:00 2017 -0600 Committer: Ted Wilmes <twil...@gmail.com> Committed: Mon Jan 23 16:47:00 2017 -0600 ---------------------------------------------------------------------- docs/src/dev/developer/release.asciidoc | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/aa262d6b/docs/src/dev/developer/release.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/dev/developer/release.asciidoc b/docs/src/dev/developer/release.asciidoc index ec1fdf6..b78e860 100644 --- a/docs/src/dev/developer/release.asciidoc +++ b/docs/src/dev/developer/release.asciidoc @@ -22,6 +22,7 @@ manager" (a committer fulfills this role), who ensures that the steps in this do multi-phased and can therefore take several weeks to complete given the time needed for Apache voting and community feedback. Once a release point has been identified, the following phases represent the flow of "release": +* Release manager key setup. * Pre-flight check. * Optionally, produce a release candidate for community feedback. * Submit the official release for PMC vote. @@ -66,6 +67,28 @@ IMPORTANT: The `clean` in the above commands is more important to the pypi deplo anything found in the `target/python-packaged/dist` directory. Since the names of the artifacts are based on timestamps, they will not overwrite one another and multiple artifacts will get uploaded. +Release Manager Requirements +---------------------------- + +If this is your first time as release manager, you will need to setup keys for signing purposes per the Apache +release process. Generally speaking, this will mean that you will need to generate a key-pair and then upload your +public key to a public keyserver. + +For a general overview of key basics, refer to link:https://www.apache.org/dev/release-signing.html#key-basics[this]. For detailed +step-by-step instructions, please follow the instructions link:https://www.apache.org/dev/openpgp.html#generate-key[here]. + +After completing the key-pair setup instructions, be sure to add yourself to the `PGP signature` section of `bin/validate-distribution.sh`. + +[source,text] +---- +echo -n " * PGP signature ... " +[ `gpg ${ZIP_FILENAME}.asc 2>&1 | grep -c '^gpg: Good signature from "Stephen Mallette <spmalle...@apache.org>"$'` -eq 1 ] || \ +[ `gpg ${ZIP_FILENAME}.asc 2>&1 | grep -c '^gpg: Good signature from "Marko Rodriguez <ok...@apache.org>"$'` -eq 1 ] || \ +[ `gpg ${ZIP_FILENAME}.asc 2>&1 | grep -c '^gpg: Good signature from "Theodore Ratte Wilmes (CODE SIGNING KEY) <twil...@apache.org>"'` -eq 1 ] || \ +{ echo "failed"; exit 1; } +echo "OK" +---- + Pre-flight Check ----------------
