DRAFT AGENDA

Date

27 Aug 2024

Attendees & Representation

Community:

M3 by July 21st
- Done (r1.1 created on 2024-08-09)
M4 Milestone (Public releases) - next steps and dates (from TSC minutes)
- August 26th (M4 release PRs available): Sub Projects should have prepared the release PRs for the public API version(s), including the release notes in CHANGELOG.md which are reflecting all changes since the last public release. Invite camaraproject/release-management_maintainers for review, don't merge before have the approval
  - If there are outstanding PRs (e.g. with test definition files) anticipate them and add remark within the release PR description that these have to be merged before
- August 30th (M4 date): all outstanding PRs merged which have to done before the creation of the public release (e.g. test definition files)
- September 5th (Approval of M4): all release PRs of Sub Project reviewed by Release Management, final approval of the Fall24 participating API releases within the TSC.

Geofencing feature file
- Not included in RC.1
- Has to be done before M4
- Last reviewed version received many comments and it is still far from being mergeable
- Discuss plan

Add handling when the requested geofence area cannot be covered
- Waiting for Commonalities (243) → still not resolved
  - Last proposal from Maximilian Laue is to use already available terminationDescription.
  - We still need to add the new terminationReason value
- Discuss plan for the short term

Update location-verification-API-Readiness-Checklist.md
- Pending point for M4 is how to fulfill mandatory requirement for "Test result statement"
- Other APIs is same situation