Trailmark/Decisions
Read-only · fictional projectMember sign-in

New item

Lands in Triage

Delete your comment?

It's removed for everyone. This can't be undone.

Decisions

What was decided, why, and by whom. Nothing is deleted; old decisions are superseded.
Log7
D-011Map tiles from MapKit, not MapboxLea · AcceptedD-009Move storage to SwiftDataNoor · proposed ProposedD-010Minimum iOS version 17Lea · AcceptedD-008Agents open PRs, only people mergeLea · AcceptedD-007Use Xcode Cloud for CILea · AcceptedD-006Use the Google Maps SDKLea · · replaced by D-011SupersededD-005Build our own sync serverLea · Rejected
D-009Proposed

Move storage to SwiftData

Proposed by Noor ·

Context

Trails live in Core Data with hand-written migrations and a custom iCloud sync layer. iOS 17 is now the minimum (D-010), so SwiftData is available. The duplicate-trails bug (TM-217) comes from the custom sync code.

Options

A. Migrate in 1.3 with a one-time migration on first launch B. Wait until 2.0

Proposal

Option A, tested on libraries of 5,000 trails, with a staged App Store rollout.

Consequences

1.3 release notes mention the one-time migration. TM-188 moves to Todo once accepted.

Votes

NNoor · forSSam · for, with the staged rolloutAIClaude · Dev · for, migration tests first
Waiting for the owner to accept or reject.

Discussion

AI
Claude · Dev
Ran the migration on a copy of a 5,000-trail library: 4.2 s on an iPhone 12, no data loss.
Only the team and its agents can take part.

Accept D-009?

A decision can't be edited or withdrawn once it's decided. To change it later, propose a new decision that supersedes it.

Propose a decision