Agenda

Antitrust Policy

• Action Items Review: Release Management Working Group
• Proposal for updated API Readiness Checklist for RM GitHub project: https://github.com/camaraproject/ReleaseManagement/issues/28
• Review proposal on versioning for API Design Guidelines: API versioning section for Commonalities API design guidelines
• Review proposal for RM GitHub on API Release Process extract: API Release Process (extract for RM GitHub)
• (Murat) Question: if we should add a process to allow for an "out-of-cycle" (fast-track) process for creating a public-release in case of a feature that was missed in the last meta-releasein case it is found between M3 and M4, that a feature is missed should we go back to alpha release, or wait till next meta-release ?
• (Tanja) Proposal to start release numbering at r1.1 - no use of 0 in release numbers
• (Jan) API family: how to handle the number for implementations for stable APIs if there are multiple APIs in the same project
• (Samuel) M0 milestone email to be prepared and sent.

Minutes

Action Items Review

• Comments

API readiness checklist

• Comments

API versioning extract

• went through all the closed items. The open items are handled on this call.

API readiness checklist for RM GitHub

• Inconsistency between GitHub proposal and Confluence. The confluence will be updated to added back in the User Stories
• Review of the checklist PR is open for review till 2024-05-23 (one week from last TSC on 2024-05-16)
• In the mean time, for thos who want to use the new checklist, the .md file can be found through this PR: Add API-Readiness-Checklist.md to RM project by tanjadegroot · Pull Request #29 · camaraproject/ReleaseManagement (github.com)

API versioning section update for Commonalities API Design Guidelines document

• Walked through the proposal - the content is open for review on confluence here: API versioning section for Commonalities API design guidelines

API Release Process extract

• Comments

Out-of-cycle public API releasefor RM GitHub

• Walked through the proposal - the content is open for review on confluence here. API Release Process (extract for RM GitHub)

Missing feature found during M3-M4. Back to alpha ?

• what if a missing feature is discovered during the M3-M4 period. can Do we need to go back to alpha .e.g adding a new path and pass a new M3 ?
• Proposed answer: The API Sub Project shall decide on the urgency and complexity of the feature.
  • If time permits to create and test an additional release-candidate then feature can be included before M4.
  • If time does not permit to properly discuss and test the missing feature, then it should be introduced in the next public-release and meta-release

Release numbers starting at r1.1

• To even further clarify the split between release numbers and API versions, the proposal is to start release numbers at r1.1, and never use 0 in release numbers. decision to be made when Herbert is back.

M0 milestone email

• The draft M0 email is here: Release Management announcements - still needs some work. Tanja de Groot & Samuel Adeyemo to discuss.

Action items

•  Prepare and send M0 announcement Tanja de Groot Samuel Adeyemo