This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 6ab8cf9 COMDEV-400 - group/sling.asc file has been removed
6ab8cf9 is described below
commit 6ab8cf92c4b47269e094b1620ccd4f453b4899b8
Author: Bertrand Delacretaz <[email protected]>
AuthorDate: Fri Sep 10 14:00:19 2021 +0200
COMDEV-400 - group/sling.asc file has been removed
---
.../documentation/development/release-management.md | 17 ++---------------
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git
a/src/main/jbake/content/documentation/development/release-management.md
b/src/main/jbake/content/documentation/development/release-management.md
index bde9b88..d32e6ec 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -402,21 +402,7 @@ Assuming you are using a \*nix system with a working
OpenSSH, GnuPG, and bash yo
When gpg asks for e-mail linked the key you *MUST USE* the
<committer>@apache.org one. When gpg asks for comment linked the key you
*SHOULD USE* "CODE SIGNING KEY"
-1. It's also good to upload your key to a public key server, see the [ASF
Infrastructure Release Signing](https://infra.apache.org/release-signing.html)
page for more info.
-
-1. Add the key to
[https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
-
- 1. Type the following command replacing the word `<e-mail>` with your
Apache's one (<committer>@apache.org) to get the key signature
-
- $ gpg --fingerprint <e-mail>
-
- The key signature is in the output following the `Key fingerprint = `
part.
-
- 1. Add the key signature into the field 'OpenPGP Public Key Primary
Fingerprint' in your profile at [https://id.apache.org](https://id.apache.org).
-
- 1. You are *DONE*, but to see the changes on
[https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
you may need to wait a few hours;
-
-1. Now add your public key to <https://downloads.apache.org/sling/KEYS> by
adding it via SVN to <https://dist.apache.org/repos/dist/release/sling/KEYS>.
This is only possible for PMC members (for a reasoning look at
[http://www.apache.org/dev/release.html#upload-ci](http://www.apache.org/dev/release.html#upload-ci)).
If you are not a PMC member, please ask one to do the upload for you. The
actual update can be achieved e.g. via
+1. Add your public key to <https://downloads.apache.org/sling/KEYS> by adding
it via SVN to <https://dist.apache.org/repos/dist/release/sling/KEYS>. This is
only possible for PMC members (for a reasoning look at
[http://www.apache.org/dev/release.html#upload-ci](http://www.apache.org/dev/release.html#upload-ci)).
If you are not a PMC member, please ask one to do the upload for you. The
actual update can be achieved e.g. via
$ svn checkout https://dist.apache.org/repos/dist/release/sling/ sling
--depth empty
$ cd sling
@@ -426,6 +412,7 @@ Assuming you are using a \*nix system with a working
OpenSSH, GnuPG, and bash yo
$ svn commit -m "my key added" KEYS
+1. It's also good to upload your key to a public key server, see the [ASF
Infrastructure Release Signing](https://infra.apache.org/release-signing.html)
page for more info.
## Appendix B: Deploy Maven plugin documentation (if applicable)
