Creation of API readiness checklist document (Issue 39) #40
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
reviewed
May 29, 2023
rartych
reviewed
May 29, 2023
documentation/API_documentation/home_devices_qod_readiness_checklist.md
Outdated
Show resolved
Hide resolved
rartych
reviewed
May 29, 2023
documentation/API_documentation/home_devices_qod_readiness_checklist.md
Outdated
Show resolved
Hide resolved
rartych
reviewed
May 29, 2023
documentation/API_documentation/home_devices_qod_readiness_checklist.md
Outdated
Show resolved
Hide resolved
rartych
approved these changes
May 29, 2023
monamok
approved these changes
May 30, 2023
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:
This PR creates a document with the API readiness checklist status according to CAMARA Commonalities.
Which issue(s) this PR fixes:
Fixes one of the topics to be resolved in Issue #39
Special notes for reviewers:
N/A
Changelog input