Prepare r2.1

[fernandopradocabrillo]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

Preparations for first pre-release of Location Insights for Fall25

Special notes for reviewers:

@chinaunicomyangfan would also like to include the DeviceVisitLocation API as part of this meta-release. The code for the proposal is in #22. Once preparations for Fall25 are applied in that PR, it can be merged and the information in changelog and readme can be updated in this PR.

cc: @FabrizioMoggio

[hdamker]

@fernandopradocabrillo I converted the PR to draft as there is no release tracker (which I need to create the release review issue) for the Fall25 release, neither for most-frequent-location nor for device-visit-location.

Please see also #28 ... decide about the scope for the Fall25 meta-release (there is no scope issue to check).

[hdamker]

@fernandopradocabrillo I had already updated README.md as part of the renaming, so would be good if you rebase and resolve the merge conflicts.

[fernandopradocabrillo]

@hdamker Fixed, I left the commit prepared on friday but didn't pushed it and didn't see your commit. It should be good now. With the release tracker that you created and the Scope Issue updated I think we can convert this PR from DRAFT to definitive_final_final_ready_to_review

[hdamker]

definitive_final_final_ready_to_review

feel free to push the button "Ready for review" :-)

[Kevsy]

Hi @fernandopradocabrillo although the IDENTIFIER_MISMATCH is removed, there is still some description related to it which should also be removed:

MostFrequentLocation/code/API_definitions/most-frequent-location.yaml

Line 528 in 6262c5e

- Inconsistency between device identifiers not pointing to the same device ("code": "DEVICE_IDENTIFIERS_MISMATCH","message": "Provided device identifiers are not consistent.").

[Kevsy]

Please see suggested changes above in comments

[jlurien]

Hi @Kevsy, @fernandopradocabrillo is on vacation this week, so he will take a look to your comments next week.

[Kevsy]

Hi @FabrizioMoggio @chinaunicomyangfan - please can you review the comments above in Fernando's absence? The M3 deadline is approaching fast (27th)

[Kevsy]

HI @fernandopradocabrillo - please can I ask you to address the comments/suggestions above, as we are now past the M3 deadline? Many thanks for your help :)

[fernandopradocabrillo]

HI @fernandopradocabrillo - please can I ask you to address the comments/suggestions above, as we are now past the M3 deadline? Many thanks for your help :)

Hi @Kevsy! Thanks for your comments, I'm on it 😄

[fernandopradocabrillo]

Hi @Kevsy, all done! you can review again whenever you can. Thanks!!

[Kevsy]

Reviewed and approved on behalf of release management 👍

Please can the codeowners perform the next steps:

• PR merged (by API repository codeowner)
• Release created within GitHub (by API repository codeowner)
• Release Tracker updated (with creation date of the release and the release tag link)

[fernandopradocabrillo]

@FabrizioMoggio please, we need tha approval of another codeowner to be able to merge the PR. Thanks!!

[hdamker]

@FabrizioMoggio @chinaunicomyangfan We would like to merge this PR today and create the release. Please let us know if it would be ok even without your review. Preferred would be your review and or approval until 15:00 UTC / 17:00 CEST.

[chinaunicomyangfan]

LGTM