Repository navigation
docs: renumber the milestones and give the field feedback a home - #433
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The board and the tree had drifted apart.
v0.6 — Stability and performanceheld seven perf issues, none started, while 59 commits landed onmainsince v0.5.0 — the Einsatzdaten dialog,SHA256SUMS.txtand 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
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:
INTERNETpermission, so joining an incident cannot work in a shipped build.Deliberately left unmilestoned: #405 (tracking), #262/#282/#87/#150 (Beyond 1.0), #337, #352, and the
good first issuebacklog, so a contributor can pick one up at any time.Also in here
docs/releasing.mdgains the two steps it never documented and nothing fails without:CHANGELOG.md's[Unreleased]/[x.y.z]link references;Side findings while checking
RemoteIncidentSession.csnow caps the joined-device attachment cache at 500 MB (fix(sync): evict the oldest attachment-cache entries once over their cap #389), but nothing deletes it when the Einsatz ends. Narrowed it on the issue to delete-on-leave and expiry before milestoning it to v0.8.Verification
Docs only, no
src/change, so noCHANGELOG.mdentry and no screenshots. EveryIssues: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