Preparing for v2 #119

Open
opened 2026-08-04 05:23:46 +00:00 by ian · 0 comments
Owner

So that we only change the API once, we need to bring in the changes from the xOTA upstream spotting branch, just disable the functionality (and comment to say that) in the 2.0 release, to be enabled later.

We also need to find a nice way to keep the V1 API running, maybe just the V2 API but with some hard-coded fudges of the data that we can remove at a later date e.g. 2.1

So that we only change the API once, we need to bring in the changes from the xOTA upstream spotting branch, just disable the functionality (and comment to say that) in the 2.0 release, to be enabled later. We also need to find a nice way to keep the V1 API running, maybe just the V2 API but with some hard-coded fudges of the data that we can remove at a later date e.g. 2.1
ian added this to the 2.0 milestone 2026-08-04 05:23:46 +00:00
ian self-assigned this 2026-08-04 05:23:46 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ian/spothole#119
No description provided.