Agenda

DRAFT

Antitrust Policy

• Action item review

• Spring25 meta-release tracking format updates

• M6: feedback

• Issues review

• AOB

Minutes

Action item review

• See Release Management Working Group - CAMARA Project - CAMARA Project (atlassian.net)

  • all done except call for maintainer

Spring25 meta-release tracking format updates

• Check Spring25 meta-release page (with test information): Meta-release Spring25 - CAMARA Project - CAMARA Project (atlassian.net)

• Check the updated release tracker page: see Test v4.5.0 - CAMARA Project - CAMARA Project (atlassian.net)

• Need to rethink the names of the release fields to be more generic

M6: feedback

Go over the M6 issues in Gitlab: Issues · camaraproject/ReleaseManagement (github.com)

• Create the r2.1 with the retrospective feedback for use in Spring25 meta-release wg management #99 opened 3 weeks ago by tanjadegroot

• Create the release r1.2 of the RM documentation for Fall24 meta-release wg management #98 opened 3 weeks ago by tanjadegroot

• Create the release r1.1 of the RM documentation wg management #97 opened 3 weeks ago by tanjadegroot

  • Herbert to make a start

• Align also Working Group release numbering with the rx.n numbering schema starting in Spring25 cycle enhancement #94 opened last month by hdamker

  • To be applied by all working groups releasing artefacts e.g. Comm, ICM, and RM - ongoing in all for Spring25 meta-release cycle

  • Update the wiki to describe approach taken @Tanja de Groot

• Naming convention for Maintenance branches and branch protection rule for them bug enhancement #93 opened last month by hdamker

  • Text to be updated by Tanja to “maintenance-rx” based on release numbers

  • Herbert to execute on the branch protection mechanism (via Governance team) on all branches “main*”

• Clarification of CHANGELOG requirements for first release candidate with previous alpha release backlog documentation #63 opened on Jul 26 by hdamker

  • Tanja to do:

  • insert the proposed text to CHANGELOG_TEMPLATE

  • update the CL EXAMPLE with and actual one

• Cross references into Commonalities, ICM and into the own API repository have to use links to a release, not into main bug release management #51 opened on Jul 25 by hdamker

  • @Herbert Damker to describe final approach and close issue. Only links at repo level shall be used, not to any file in the repo.

  • Check for links in the RM documentation in GitHub @Tanja de Groot

Issues review

• NumberVerification r1.3 patch release review review #103 opened 5 days ago by hdamker 9 of 12 tasks

  • done. closed on the call

• Internal links in a release API spec enhancement #101 opened 2 weeks ago by jlurien

  • this is a bug

  • need to enhance the review checklist to check that all links are local to the release. - could need a GitHub checking tool

• ICM r0.2.1 patch release review review #100 opened 2 weeks ago by hdamker 8 of 11 tasks

  • Herbert to do final review allowing merge to be done

• API Versioning - Aggregation backlog question release management #14 opened on Jul 6, 2023 by chrishowell

  • keep as backlog

AOB

• New sub projects (of Sandbox type): do we need better/different guidelines to do releases outside the meta-release ? Answer: no different guidelines are needed, only the meta-release labels on the API tracker should be changed to “camara-sandbox” (once the Sandbox concept is officially endorsed).

  • Check text on release numbering and connection to meta-release

Action items