NFR-OPS-4 — update and first run are undefined. There is no update mechanism of any kind.
The concrete reason the requirement gives
D2 pins rawler at a non-SemVer alpha. Its camera-support fixes are exactly the changes users will need — a body that does not decode today decodes after an upgrade — and there is no path by which a user receives one.
That makes this less "we should have auto-update" and more "the RAW support story has no delivery mechanism".
Undefined
What happens on first run — the launch flow exists, but nothing states what a new install is entitled to assume.
How an update reaches a user on each of the five channels in distribution.md §1.
Whether the catalog schema migration path is exercised on upgrade, or only on a fresh build.
Note
Two of those five channels currently exist as decisions rather than recipes (AppImage, F-Droid), so part of this answer is blocked on writing them.
See docs/outstanding.md §5.
**NFR-OPS-4 — update and first run are undefined.** There is no update mechanism of any kind.
## The concrete reason the requirement gives
**D2 pins rawler at a non-SemVer alpha.** Its camera-support fixes are exactly the changes users will need — a body that does not decode today decodes after an upgrade — and there is no path by which a user receives one.
That makes this less "we should have auto-update" and more "the RAW support story has no delivery mechanism".
## Undefined
- [ ] What happens on first run — the launch flow exists, but nothing states what a *new* install is entitled to assume.
- [ ] How an update reaches a user on each of the five channels in `distribution.md` §1.
- [ ] Whether the catalog schema migration path is exercised on upgrade, or only on a fresh build.
## Note
Two of those five channels currently exist as decisions rather than recipes (AppImage, F-Droid), so part of this answer is blocked on writing them.
See `docs/outstanding.md` §5.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
NFR-OPS-4 — update and first run are undefined. There is no update mechanism of any kind.
The concrete reason the requirement gives
D2 pins rawler at a non-SemVer alpha. Its camera-support fixes are exactly the changes users will need — a body that does not decode today decodes after an upgrade — and there is no path by which a user receives one.
That makes this less "we should have auto-update" and more "the RAW support story has no delivery mechanism".
Undefined
distribution.md§1.Note
Two of those five channels currently exist as decisions rather than recipes (AppImage, F-Droid), so part of this answer is blocked on writing them.
See
docs/outstanding.md§5.