Page History

...

• 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
• Actions towards M3:
  •  Type your task here, using "@" to assign to a user and "//" to select a due date

Functionality

• Add handling when the requested geofence area cannot be covered
  • Waiting for Commonalities
• Update maxAge-behaviour for /verify & /retrieve
  • Review comments in issue
  • Decide on 422 vs 200 + UNKNOWN

Alignment with Commonalities

Errors

• geofencing: Alignment of errors with Commonalities
  • 1 approval
  • 1 comment suggesting to not include all possible HTTP codes. This issue was also discussed in QoD
• https://github.com/camaraproject/QualityOnDemand/issues/305location-retrieval: Alignment of errors with Commonalities
  • 1 approval with comments
• location-verification: Alignment of errors with Commonalities
  • 2 approvals

New: device input

• Align device object with Guidelines
  • Make device optional
  • Add some new doc to info.description

Test plans

All with some comments, still not approved:

...

• Issues created and linked in DeviceLocation API Release Tracking
  • Scope of Location Verification API for Fall24 CAMARA Meta Release
  • Scope of Location-Retrieval for Fall24 CAMARA Release
  • Scope of Geofencing Subscriptions API for Fall24 CAMARA Meta Release
• Review if we need to update anything

Other New

• Issue: Add an “Area” data-type into CAMARA_common.yaml
  • Referencing Commonalities issue 

...