Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Enable markdownlint rule MD005 #1167

Merged
merged 1 commit into from
Dec 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/linters/.markdown-lint.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,6 @@
# https://github.com/DavidAnson/markdownlint#rules--aliases
MD001: false
MD004: false
MD005: false
MD007: false
MD009: false
MD010: false
Expand Down
24 changes: 12 additions & 12 deletions docs/community/release-manager.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,18 +39,18 @@ JAVA_HOME="${JAVA_HOME:-$(/usr/libexec/java_home -v 1.8)}" exec "/usr/local/Cell

1. Install GNUGPG if it was not installed before. On Mac: `brew install gnupg gnupg2`
2. Generate a secret key. It must be RSA4096 (4096 bits long).
* Run `gpg --full-generate-key`. If not work, run `gpg --default-new-key-algo rsa4096 --gen-key`
* At the prompt, specify the kind of key you want: Select `RSA`, then press `enter`
* At the prompt, specify the key size you want: Enter `4096`
* At the prompt, enter the length of time the key should be valid: Press `enter` to make the key never expire.
* Verify that your selections are correct.
* Enter your user ID information: use your real name and Apache email address.
* Type a secure passphrase. Make sure you remember this because we will use it later.
* Use the `gpg --list-secret-keys --keyid-format=long` command to list the long form of the GPG keys.
* From the list of GPG keys, copy the long form of the GPG key ID you'd like to use (e.g., `3AA5C34371567BD2`)
* Run `gpg --export --armor 3AA5C34371567BD2`, substituting in the GPG key ID you'd like to use.
* Copy your GPG key, beginning with `-----BEGIN PGP PUBLIC KEY BLOCK-----` and ending with `-----END PGP PUBLIC KEY BLOCK-----`.
* There must be an empty line between `-----BEGIN PGP PUBLIC KEY BLOCK-----` and the actual key.
* Run `gpg --full-generate-key`. If not work, run `gpg --default-new-key-algo rsa4096 --gen-key`
* At the prompt, specify the kind of key you want: Select `RSA`, then press `enter`
* At the prompt, specify the key size you want: Enter `4096`
* At the prompt, enter the length of time the key should be valid: Press `enter` to make the key never expire.
* Verify that your selections are correct.
* Enter your user ID information: use your real name and Apache email address.
* Type a secure passphrase. Make sure you remember this because we will use it later.
* Use the `gpg --list-secret-keys --keyid-format=long` command to list the long form of the GPG keys.
* From the list of GPG keys, copy the long form of the GPG key ID you'd like to use (e.g., `3AA5C34371567BD2`)
* Run `gpg --export --armor 3AA5C34371567BD2`, substituting in the GPG key ID you'd like to use.
* Copy your GPG key, beginning with `-----BEGIN PGP PUBLIC KEY BLOCK-----` and ending with `-----END PGP PUBLIC KEY BLOCK-----`.
* There must be an empty line between `-----BEGIN PGP PUBLIC KEY BLOCK-----` and the actual key.
3. Publish your armored key in major key servers: https://keyserver.pgp.com/

### 3. Use SVN to update KEYS
Expand Down