Community Attendees:

Tanja de Groot Herbert Damker Samuel Adeyemo Ming Hui Foo 

Community Attendees:

Rafal Artych Ludovic Robert Jose Luis Urien Murat Karabulut 

LF Staff:

Casey Cain 

Agenda

Antitrust Policy

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

Minutes

  • Action Items Review

done


Closing review issues

  • DeviceLocation - OK
  • ConnectivityInsights: 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

1 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/


2 Clean up fall24 page

We need to clean-up https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24 ... as a lot of the information is no longer relevant.

The information should be "fixed" so that accidential changes to the release trackers will not change the content of the Meta-release. 

  • Move the current information one level lower (history part) or at the end of the current page
  • use the overview slide with API to document the Meta-Release also within the wiki.


3 Review RM Slides

  • All to review slides and comment (add as attachment to this page).

Add API picture w/o release numbers to the Fall24 meta-release. Tanja de Groot 

4 API downloads

Think about creating an M5 artefact - a zipfile with all meta-release APIs - issue is maintenance in case of patch releases 

Add a yaml field to the API Release tracker template. 

6:1

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.1) but as we haven't given the artefacts a version we might not need that).
  • TO DO (in GiHub):
    • write a Changelog for r1.1 (RM #35) and do r1.2 now - create a release issue. 

    • 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 ...). 

Commonalities and ICM to create release iso version issue #94 

Action items

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