Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scope of geofencing-subscriptions API for Spring25 Meta Release #280

Open
jlurien opened this issue Dec 11, 2024 · 1 comment
Open

Scope of geofencing-subscriptions API for Spring25 Meta Release #280

jlurien opened this issue Dec 11, 2024 · 1 comment
Assignees
Labels
Spring25 subproject management Indicating issues with subproject repository or release management process

Comments

@jlurien
Copy link
Collaborator

jlurien commented Dec 11, 2024

Problem description
This issue shall define which issues are within scope of Geofencing Subscriptions API for the Spring25 release and will be regularly updated based on the decision within the Device Location API meetings.

Expected action
Tentative issues to be included:

@jlurien jlurien added subproject management Indicating issues with subproject repository or release management process Spring25 labels Dec 11, 2024
@bigludo7
Copy link
Collaborator

@maxl2287 A small one also to consider is related to maxEvents. If you check the guideline here there is a note on initialEvent:

Note on combined usage of initialEvent and subscriptionMaxEvents: Unless explicitly decided otherwise by the API Sub Project, if an event is triggered following initialEvent set to true, this event will be counted towards subscriptionMaxEvents (if provided). It is recommended to provide this clarification in all subscription APIs featuring subscriptionMaxEvents and initialEvent.

So probably worth to add a note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Spring25 subproject management Indicating issues with subproject repository or release management process
Projects
None yet
Development

No branches or pull requests

3 participants