update instructions to edit KEYS in Git #453
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
note for self: next step is to update https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-check-pgp-keys.html |
slawekjaranowski
approved these changes
Mar 8, 2025
|
another idea: we could probably ease PMC publication process with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
KEYS files history was imported from svn in #240
now we can have committers edit in Git like they do with any other committer content
and PMC members publish to dist area https://dlcdn.apache.org/maven/ (through svn https://dist.apache.org/repos/dist/release/maven)
This workflow is easier to follow (and even understand because edit in Git and publish in svn creates less confusion between the edit and publish urls)