docs(req): add FR-UI-UPD-02 (automatic update check + notification) - #179
Merged
Conversation
Records a new requirement, requested by DC0SK; not yet implemented. An automatic check for a newer release, on by default, opt-out in Settings, with a notification in the top status area beside the connection indicator as a clickable link to the release page. Recorded as a deliberate relaxation of FR-UI-UPD-01, which made the update check manual-only precisely to avoid unannounced outbound connections on a possibly-metered remote link. The automatic check is constrained to bound that cost: opt-out, once per start rather than on a timer, and silent unless it finds a substantiated (never spurious) newer release - so a metered link sees at most one small request per launch, and only a real update draws attention. Marked priority C, so the gate does not require a test until it is built. Also fixed merge artifacts in two doc frontmatters: the SRS had two version: keys (0.48 and a stray 0.40) and the user manual had two updated: keys. Both were invalid YAML from keep-both conflict resolution; set to single, current values. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KiAgfnGv746wwVBSfFkoRY
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
1 participant
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.
Records a new requirement, requested by @dc0sk. Not yet implemented — this is the requirement, not the feature.
FR-UI-UPD-02
Automatically check for a newer release on start-up, on by default, opt-out in Settings. When a substantiated newer release is found, a notification appears in the top status area beside the connection indicator, as a clickable link to the release page.
Recorded as a deliberate relaxation, not an oversight
FR-UI-UPD-01deliberately made the update check manual-only — "a radio-control app should not make unannounced outbound connections, and a remote station may be on a metered link." This new requirement reverses that by choice, so it's constrained to bound the cost:FR-UI-UPD-01's numeric, never-spurious comparisonSo a metered link sees at most one small request per launch, and only a genuine update ever draws attention. Marked priority C, so the traceability gate doesn't require a test until it's built.
Also: two frontmatter fixes
While here I fixed merge artifacts in two doc frontmatters — the SRS had two
version:keys (0.48 and a stray 0.40), the user manual twoupdated:keys. Both were invalid YAML from keep-both conflict resolution during the release churn. Now single, current values; a scan confirms no other doc has duplicate frontmatter keys.Docs-only.
🤖 Generated with Claude Code
https://claude.ai/code/session_01KiAgfnGv746wwVBSfFkoRY