Agenda

Antitrust Policy

DRAFT

• Agenda review

• Action Items Review: see Release Management Working Group

• Open Issue Review

• Include meta-release name in API release number (x=24f iso x=1)

• Do joint M0/M1 announcement

Minutes

Action Item review

Action RM team: add another CODEOWNER

How to request review on RM issues. Option would be to use the codeowner & RM mailinglist

Action TdG to send email to RM mailing list for review of the RM extract PR

Open Issue Status

Add API Release Guidelines (process extract) to RM project documentation

#30 opened 2 weeks ago by tanjadegroot

Action Tanja to send message to RM mailing list

Add new API readiness checklist documentation

#28 opened 2 weeks ago by tanjadegroot

One more week for the team to comment - action to send email to RM mailing list

Create a CHANGELOG_TEMPLATE.md within ReleaseManagement/documentation & update it according to API Release Process documentation

#25 opened 2 weeks ago by hdamker

• DRAFT available here: camaraproject-ReleaseManagement/documentation/CHANGELOG_TEMPLATE.md at Update-of-Changelog-template · nokia/camaraproject-ReleaseManagement (github.com)

• Questions disucssed: 

  • Should there be a Changelog per API if more that one API in a Sub Project, or should all be in the same Changelog ?

  • Answer: One Changelog for all APIs as only very closely related APIs should be present in one repository.

  • If one Changelog for multiple APIs how would APIs be ordered in the file?

  • Answer: at each release, a section shall be added at the top of the file with the changes for all APIs.

• Add a section with examples to the Changelog file

Is there a need for association of API definition (yaml) to Commonalities, ICM or Meta Release version? enhancement

#27 opened 3 weeks ago by gmuratk

Leave open for comments till next week

Consolidation Issue for open points release management documentation release management

#9 opened on Oct 4, 2023 by shilpa-padgaonkar

Should resolve at the end

Development and Release Branches documentation release management

#10 opened on Oct 3, 2023 by FabrizioMoggio

TdG to add comment on current proposal so issue can be closed

Define mandatory end points URL in each project release management

#11 opened on Sep 13, 2023 by psidana1983

To be transferred to Gvernance (action from 2024-05-14)

 Process to publish v1.0 of an API

#5 opened on Jul 25, 2023 by Kevsy

Action TdG: Add comment so it can be closed

Define Release Management for CAMARA

#4 opened on Jul 21, 2023 by MarkusKuemmerle

Should be near to closure :-) 

API Versioning - Aggregation backlog question release management

#14 opened on Jul 6, 2023 by chrishowell

Action TdG: to be checked - Backlog item

Readiness Checklist step 6 update proposal release management

#16 opened on Jun 22, 2023 by FabrizioMoggio

Action TdG: add a comment on readiness checklist update

Do joint M0/M1 announcement

• Proposed to do a joint M0/M1 announcement at M1 (targeted for 31/05/2024, likely to shift to week after due to holidays)

Include meta-release name in API release number or in OAS file

• Issue #27 presented: Is there a need for association of API definition (yaml) to Commonalities, ICM or Meta Release version? · Issue #27 · camaraproject/ReleaseManagement (github.com)

• Other comments welcome. Will need a decision by next week.

AOB

• put release tracking pages iso tracket page under each API project TdG to check with Evan

• put this in the M0/M1 announcement

Action items