Deprecate API-Readiness-Checklist.md #220
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
rartych
changed the title
PedroDiez
reviewed
Jun 10, 2024
rartych
requested review from
shilpa-padgaonkar,
patrice-conil and
RubenBG7
as code owners
The old content was removed
|
I have removed the old content (table). |
Co-authored-by: Shilpa Padgaonkar <[email protected]>
|
@patrice-conil Could you approve also this PR? |
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.
What type of PR is this?
What this PR does / why we need it:
The API-Readiness-Checklist.md is replaced by the new updated version which is located in the Release Management project.
It should be approved after merging camaraproject/ReleaseManagement#29 .
Which issue(s) this PR fixes:
Fixes #202
Special notes for reviewers:
I am not aware of references to the current API Readiness Checklist from other Commonalities documents.
Using Markdown
strikeoutformatting breaks table rendering, it may be clearer to keep the original table without strikeout.Changelog input
Additional documentation