Date

Jul 30, 2024

Attendees & Representation

Community: @Jose Luis Urien Pinedo @Cetin Alpaycetin @Fernando Prado Cabrillo @Rafal Artych

M3 by July 21st
- First RC to be published
- This is not a hard deadline. Subprojects may reduce the period between M3 and M4
M4 by August 31st
- Hard deadline to have all final contents for meta-release approved

geofencing: Add SUBSCRIPTION_DELETED as termination-reason
- Approved
- Merged
geofencing: Alignment of errors with Commonalities
- Approved
- Merged
Add handling when the requested geofence area cannot be covered
- Waiting for Commonalities (243) → still not resolved
- Should we postpone post meta-release? @Ludovic Robert in favour of this (Slack conversation)
  - @Jose Luis Urien Pinedo proposes to wait for the outcome of Commonalities (for future version or for future RC if decision happens before M4)
location-verification Create Location Verification User Story
- Comments to be resolved
- Required for M4
  - Not blocking rc.1
  - Has to be done before M4
Geofencing feature file
- Comments pending
- Still far from complying with guidelines
- Should we postpone after r1.1 ?
  - Agreed to keep it open and do not include it in RC.1
  - Has to be done before M4
Create PR for r1.1
- README
- CHANGELOG
- YAML specs with versions updated to -rc.1
- *.feature assets if ready
- @Jose Luis Urien Pinedo will create the PR

There are some discussions in Commonalities (e.g.) and other WGs that may impact our APIs for Meta-Release
- Align with decisions in Commonalities and ICM, if happen