Add a RELEASE.md file outlining the release process#94
Merged
Conversation
joshbainbridge
commented
Jun 24, 2026
joshbainbridge
force-pushed
the
add-release-doc
branch
2 times, most recently
from
June 24, 2026 23:15
3b52d23 to
05bc116
Compare
As described in the ASWF project lifecycle guidelines, all projects should document their release process. Create a RELEASE.md file with the methodology, cadence, criteria for cutting a new release. Also fill in some similar missing information from the SUPPORT.md file. This resolves #91. Signed-off-by: Josh Bainbridge <josh.bainbridge@gmail.com>
joshbainbridge
force-pushed
the
add-release-doc
branch
from
June 28, 2026 14:45
05bc116 to
77f3273
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 described in the ASWF project lifecycle guidelines, all projects should document their release process.
Create a RELEASE.md file with the methodology, cadence, criteria for cutting a new release. Also fill in some similar missing information from the SUPPORT.md file.
This resolves #91.