RFE: add proper release process docs #94
Closed
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
The mailing list has been deprecated and made read-only, remove references from the README.md file. Signed-off-by: Paul Moore <paul@paul-moore.com>
Update our release process and README documentation based on our current plans. These docs can (and should!) be updated as needed to reflect changes in our processes. Signed-off-by: Paul Moore <paul@paul-moore.com>
There was a problem hiding this comment.
Looks good to me. Thanks, @pcmoore
Acked-by: Tom Hromatka <tom.hromatka@oracle.com>
drakenclimber
approved these changes
May 10, 2022
kolyshkin
reviewed
May 12, 2022
kolyshkin
approved these changes
May 12, 2022
|
Merged at aa8bb55. |
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.
As discussed in #36, this PR adds an initial release process and updates the README.md with information on verifying signed git tags as well as the maintainer's GPG key fingerprints.
Feedback, especially on verifying golang module signed release tags is welcome.