Skip to content

Clarify signing key checks before release votes - #714

Merged
dongjoon-hyun merged 3 commits into
apache:asf-sitefrom
szehon-ho:codex/release-keys-instructions
Nov 13, 2026
Merged

dongjoon-hyun merged 3 commits into
apache:asf-sitefrom
szehon-ho:codex/release-keys-instructions

Conversation

@szehon-ho

@szehon-ho szehon-ho commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

Release vote emails link to the published release KEYS file. A release manager's
signing key must be present there so voters can verify the candidate.

Document that release managers should check the release KEYS file before starting a
vote. If their key is missing, PMC members can add it themselves; other release
managers should ask their PMC shepherd to add it.

This follows the guidance in apache/spark#59811.

Validation: built the site with Jekyll 4.4.1 in a Ruby 3.4 Docker container, checked
the rendered KEYS guidance and links, and ran git diff --check.

Generated-by: Codex (GPT-6)

@szehon-ho szehon-ho changed the title Clarify signing key setup for non-PMC release managers Clarify signing key checks before release votes Oct 27, 2026
@szehon-ho

Copy link
Copy Markdown
Member Author

@dongjoon-hyun @HyukjinKwon does it make sense? given the discrepancy in apache/spark#59811. happy to change the language any way

Comment thread release-process.md Outdated
```

And then append the generated key to the KEYS file by:
And then append the generated key to the staging KEYS file by:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I remember a few years ago (I cannot find the exact email, it happened in the incubating list, many incubating projects were coached there on how to perform an Apache release), ASF asked us to always use .../release/<project>/KEYS in the voting email instead of .../dev/<project>/KEYS.

So we don't need to maintain the .../dev/spark/KEYS actually, and the command can be updated in-place to point to the .../release/<project>/KEYS

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, hm. This came when i was trying to do the release, committer can only append keys to dev//KEYS, but not release//KEYS, the latter is automatically populated once release is done iiuc.

the problem is, the VOTE email points to the release KEYS so nobody can validate until that happens and I get some -1 vote. just a one-time problem though. Not sure the solution

dongjoon-hyun
dongjoon-hyun approved these changes Nov 13, 2026 •

@dongjoon-hyun dongjoon-hyun left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops. I missed 142 line in the previous approval. So, I removed it.

To @szehon-ho , we can add line 150 ~ 154, because it's the Apache Spark way.

@dongjoon-hyun dongjoon-hyun left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @szehon-ho .

@dongjoon-hyun
dongjoon-hyun merged commit 6b6a589 into apache:asf-site Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants