Skip to content

docs: renumber the milestones and give the field feedback a home - #433

Merged
DeepDiver1975 merged 1 commit into
mainfrom
docs/roadmap-milestone-shift
Sep 20, 2026
Merged

DeepDiver1975 merged 1 commit into
mainfrom
docs/roadmap-milestone-shift

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Contributor

Why

The board and the tree had drifted apart. v0.6 — Stability and performance held seven perf issues, none started, while 59 commits landed on main since v0.5.0 — the Einsatzdaten dialog, SHA256SUMS.txt and Sigstore attestations, the Datenschutzseite, the Sicherheitstrupp, Trupp-Typ rules in the Stammdaten, the PDF and Übersicht fixes — belonging to no milestone at all. On top of that ~26 issues arrived unscheduled: the portability review (#399–#405) and the first Übung's feedback (#410–#429).

So 0.6 is cut where the work actually is, and every theme shifts one version up.

The new ladder

Milestone Open What it is
v0.6 — Field fixes and verifiable releases (new) 8 what the tree already contains, plus the bugs the Übung found
v0.7 — Stability, performance and field polish 12 the Sept 2026 perf review + UX corrections that change no file format
v0.8 — Security and trust 9 sync/Android hardening, logging, + EXIF stripping and cache lifetime
v0.9 — Install without warnings 3 unchanged
v0.10 — i18n and architecture 10 + everything hardcoding a Bavarian concept, all waiting on #350
v0.11 — New incident modules and Stammdaten (new) 8 Dekon, freie Gase, Häuser, Einsatzpläne, address model
v1.0 — File format freeze 1 unchanged — 1.0 stays the data promise, not a feature count

The version numbers keep climbing in 0.x rather than jumping to 1.0, because 1.0 is a promise about your data and the schema is not ready to stand still yet.

How the feedback was split

By what it costs, not by who asked:

Deliberately left unmilestoned: #405 (tracking), #262/#282/#87/#150 (Beyond 1.0), #337, #352, and the good first issue backlog, so a contributor can pick one up at any time.

Also in here

docs/releasing.md gains the two steps it never documented and nothing fails without:

  • repointing CHANGELOG.md's [Unreleased] / [x.y.z] link references;
  • rolling the milestone over at release time, instead of leaving issues to lose it silently.

Side findings while checking

Verification

Docs only, no src/ change, so no CHANGELOG.md entry and no screenshots. Every Issues: line was checked programmatically against the live milestone contents — all seven match, and the set of open issues with no milestone is exactly the deliberate list above.

🤖 Generated with Claude Code

0.6 was the perf milestone on the board while the tree had turned it into a
large fix-and-docs release: 59 commits since v0.5.0 — the Einsatzdaten dialog,
checksums and Sigstore attestations, the Datenschutzseite, the Sicherheitstrupp,
the PDF and Übersicht fixes — none of which belonged to any milestone, and seven
perf issues in v0.6 of which none had been started.

Cut 0.6 where the work actually is, and shift every theme one version up:
stability and performance to 0.7, security to 0.8, install to 0.9, i18n and
architecture to 0.10. 1.0 stays what it always was, the file-format freeze; the
ladder simply keeps climbing in 0.x until the schema is ready to stand still.

The ~26 issues that arrived since — the portability review and the first Übung's
feedback — are split by what they cost rather than by who asked. Bugs that lose
input or a click go into 0.6, including an Android APK that declares no INTERNET
permission and therefore cannot join an incident at all. UX corrections that
change no file format join the perf work in 0.7. Everything hardcoding a
Bavarian concept waits on #350's localization decision in 0.10. The rest add a
module or a Stammdaten table, so they become a new 0.11 — deliberately before
the freeze, because afterwards each of them costs a forward migration that has
to keep working for good.

docs/releasing.md gains the two steps it never documented and nothing fails
without: repointing CHANGELOG.md's link references, and rolling the milestone
over instead of leaving issues to lose it silently.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
@DeepDiver1975
DeepDiver1975 merged commit a3703f1 into main Sep 20, 2026
6 checks passed
@DeepDiver1975
DeepDiver1975 deleted the docs/roadmap-milestone-shift branch September 20, 2026 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant