Rename v4 to ROADMAP
v4 was always just the server-dependent programme (group rides, accounts, paid backup) plus V3-17. Renaming it to ROADMAP since it's about to become the home for an incoming list of bugs and features that need triage ahead of the next v3-style ticket batch -- that triage takes priority over the existing server-dependent items, none of which are blocking.
This commit is contained in:
@@ -13,7 +13,7 @@
|
||||
|
||||
---
|
||||
|
||||
# Backlog — v3 and v4
|
||||
# Backlog — v3 and the ROADMAP
|
||||
|
||||
Everything known-outstanding, with enough context to pick up cold. Nothing here is
|
||||
committed to — it is a menu, roughly ordered by value.
|
||||
@@ -21,9 +21,12 @@ committed to — it is a menu, roughly ordered by value.
|
||||
**v3 is now broken out into tickets: [v3/README.md](v3/README.md).** This document stays
|
||||
as the reasoning; the tickets are the executable form.
|
||||
|
||||
**v3 is everything that can be built with no server.** **v4 is everything that cannot.**
|
||||
That split is the most useful thing in this document: it means v3 can proceed indefinitely
|
||||
without anyone deciding to run infrastructure or hold other people's location data.
|
||||
**v3 is everything that can be built with no server. The ROADMAP is everything that
|
||||
cannot, plus whatever bugs and features come up that need triage before the next v3-style
|
||||
ticket batch.** The no-server split is still the most useful structural fact in this
|
||||
document: it means v3 can proceed indefinitely without anyone deciding to run
|
||||
infrastructure or hold other people's location data. The ROADMAP is where everything else
|
||||
gets managed first.
|
||||
|
||||
**Before planning anything: run the real-ride checklist in
|
||||
[the real-ride checklist](port/REAL-RIDE-CHECKLIST.md).** Several items below may turn out to be non-issues, and
|
||||
@@ -230,8 +233,8 @@ Terse on purpose. Unshaped, to be consolidated later.
|
||||
### Threads running through these
|
||||
|
||||
Sign-up, cloud backup and group ride are one programme, not three: they all need a server,
|
||||
identity, and a privacy stance. They have therefore been moved out to **v4** below, and
|
||||
should be scoped together or not at all.
|
||||
identity, and a privacy stance. They have therefore been moved out to the **ROADMAP**
|
||||
below, and should be scoped together or not at all.
|
||||
|
||||
Activity type (now section 4) and theming are independent and much cheaper — either could
|
||||
ship alone, and activity type is the natural first v3 task because it forces the migration
|
||||
@@ -246,7 +249,15 @@ entirely standalone.
|
||||
|
||||
---
|
||||
|
||||
# v4 — everything that needs a server
|
||||
# ROADMAP
|
||||
|
||||
Formerly "v4." Renamed because it now holds more than the server-dependent programme
|
||||
below: it's also where Dylan's running list of bugs and features gets triaged before
|
||||
becoming its own ticket batch, the way v3 was broken out. That triage takes priority over
|
||||
the items below — nothing here is blocking, all of it has been waiting since before v3
|
||||
started.
|
||||
|
||||
## The server-dependent programme
|
||||
|
||||
Split out from v3 deliberately. These three are **one programme, not three items**: each
|
||||
needs a server, an identity system, and a privacy stance, and none of them is worth
|
||||
|
||||
Reference in New Issue
Block a user