You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Marketing] API description review for M4 meta-release (Sync26): device-media-streaming-rate #56
The M4 release (31 Oct 2026) must include the necessary updates of the API descriptions in the wiki, which is the base for the CAMARA website. API owners own their descriptions as long as they comply with the Marketing guidelines.
What we ask the API owners
Review the content of this API's wiki page against the Checklist for API description reviews, limited to the content points below. Reference links, as provided in the original issue: camaraproject.org (there's not an entry available) with the latest version in the API wiki).
Update the wiki page if needed.
Confirm in this issue that the wiki page reflects the API definition(s) in the M4 (Sync26 public) Release Review.
Tell us whether the wiki page changed due to the new meta-release (Sync26). Reply with "No changes" or a short summary of what changed, so Marketing can identify the updates.
Checklist: content to verify (API owner)
API description: targets and functionality are complete and understandable
Use cases: understandable; name in bold; link to the GSMA Use Case Library where appropriate
Benefits: understandable; name in bold
Confirmation
Please reply in this issue with:
The wiki page reflects the API definition(s) in the M4 (Sync26 public) Release Review.
Changes due to the new meta-release (Sync26): No changes, or a short summary of what changed.
Deadline for this confirmation: before the M4 release (31 Oct 2026).
What Marketing does (no action needed from the API owner)
Once the Sync26 releases are public, Marketing checks the remaining fields against the repositories, scripted where possible, and updates the website: API Portfolio, Sub Project Wiki, API Wiki, API Repository and its status, API status, versions and release dates, API availability, and the visual of typical use cases.
After your confirmation, Marketing completes these fields and closes this issue.
Closing this issue for now. Following the feedback in camaraproject/Marketing#100 (comment), an API is added to the website at the earliest when it has a reviewed and approved release candidate, so a description review is not needed yet. The review will be requested again once a release candidate is approved. No action is needed from the code owners for now.
Activity
albertoramosmonagas commentedon Oct 22, 2026
Closing this issue for now. Following the feedback in camaraproject/Marketing#100 (comment), an API is added to the website at the earliest when it has a reviewed and approved release candidate, so a description review is not needed yet. The review will be requested again once a release candidate is approved. No action is needed from the code owners for now.