admin: add line 13 (API description for marketing) to API readiness checklists #280
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.
CAMARA Project Admin Update
This pull request adds the new line 13 (API description for marketing) to existing API-Readiness-Checklist.md files to align them with the latest template.
Changes:
New line added:
Requirements by release stage:
This ensures all API readiness checklists include the marketing description requirement that becomes mandatory for public releases.
Files modified: ./documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md ./documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md ./documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md ./documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md ./documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md ./documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
🔧 Generated via project-admin workflow
Triggered by hdamker, executed via hdamker-bot
➡️ Next Steps: This PR should be reviewed, approved, and merged by repository codeowners following standard review processes.
This is a manually triggered automated administrative update.