Agenda

Antitrust Policy

• Action Items Review
• Closing review issues
• M5 actions
  • clean up of Fall24 page
  • add a page in GitHub
  • and more ?
• Create a RM release: (existing action 

  • Herbert: We still have the action item open to create a release of the Release Management repository.I looked a little bit through the history of the repository and have found that there is #35 with the last larger change of the repository ("Update public release name") which was merged on July 4th (shortly before the release candidates of Commonalities and ICM). That could be candidate for r1.1 (if using a version it would be something as 0.1.0-rc) but as we haven't give the artefacts a version we might not need that).And then we can create now a r1.2 which indicates the artefacts used for the Fall24 Meta-Release.After the retrospective and its changes we would than create a r2.1. With the meaning that this is the version of RM supposed to be used for Spring25 (as long as we don't need to fix something). Could be done until M0 or M1 (or two release until then ...). (edited) 

    
    

Minutes

• Action Items Review

done

Closing review issues

DeviceLocation - OK

ConnectivityInsighte: blocked on easyCLA CR #98 

SimpleEdgeDiscovery - waiting for 1 approval

PopulationDensity - waiting to confirm test definition is solved and merged - then ok for release;

Target to close all by Wed 11/09/2024 - declare M4 by release Mgmt

M5 actions

Add page in github

We wanted to make an overview page for the GitHub organization - with the APIs in the Meta-Release

See https://github.blog/changelog/2021-09-14-readmes-for-organization-profiles/

Clean up fall24 page

We could also think about to clean-up https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24 ... lot of the information is no longer relevant. Also the information should be "fixed", that accidential changes to the release trackers will not change the content of the Meta-Release. Maybe moving the current information one level lower, and use the overview slide with API + the page in 2. to document the Meta-Release also within the wiki?

Slides on RM - Herbert to add

6:17

Herbert Damker
Regarding 2.: I can try how a page can be created on this level (and how it will be shown be GitHub)

Create a RM release: (existing action 

• • Herbert: We still have the action item open to create a release of the Release Management repository.I looked a little bit through the history of the repository and have found that there is #35 with the last larger change of the repository ("Update public release name") which was merged on July 4th (shortly before the release candidates of Commonalities and ICM). That could be candidate for r1.1 (if using a version it would be something as 0.1.0-rc) but as we haven't give the artefacts a version we might not need that).And then we can create now a r1.2 which indicates the artefacts used for the Fall24 Meta-Release.After the retrospective and its changes we would than create a r2.1. With the meaning that this is the version of RM supposed to be used for Spring25 (as long as we don't need to fix something). Could be done until M0 or M1 (or two release until then ...). (edited) 

• Comments

Action items

• After update to new wiki - check the the timeline figure.