{{ message }}
Fix #1202 - Add release documentation and comply with source package naming requirements#1203
Merged
Conversation
…naming requirements
dave2wave
approved these changes
Apr 30, 2024
dave2wave
left a comment
dave2wave
left a comment
Member
There was a problem hiding this comment.
Please consider my comments, but generally I approve.
Contributor
Author
dave2wave
approved these changes
Apr 30, 2024
Contributor
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
3 participants
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.
Hi all,
can you do a careful check, if the RELEASE docs comply with the incubator requirements and are technically correct?
I don't really now the specifics for the incubator, but should cover the content from https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Gruß
Richard