These pieces of owner review 5 (v1.1.0, PR #68) were left out of the release:
- **#67 share:** a read-only Windows Firewall status row in the Server section. Chronos adds no firewall rule, and Windows shows its own prompt.
- **#66 homes:**
- *Change…* and *Forget* on Settings › Server › Known servers;
- a "Sorting folders…" status line while the 1.0 layout is being sorted;
- the render-node cache uses the address folder until the first reconnect;
- `CurrentArchive.Pick` can still pick a per-server originals archive.
- **#66 discovery:** the LAN beacon does not announce `serverId` yet, so discovery cannot recognise a server whose address changed before sign-in.
- **#65 progress:** the server's `ProgressGate` has no trailing publish for render-node reports.
- **docs/ui:** `DESIGN.md` §4 and the mockups (Jobs, Server, Admin, Archive, Settings, Uploader, setup) are not updated for the new screens.
- **Tests:**
- #67 "own share recognised while starting" has no automated test;
- the send-job server-id compare has no test of its own;
- the tray, window and dialogs are not driven together by a test (the UI wiring classes hang on the dev PC).
Refs #64 #65 #66 #67
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.
These pieces of owner review 5 (v1.1.0, PR #68) were left out of the release:
CurrentArchive.Pickcan still pick a per-server originals archive.serverIdyet, so discovery cannot recognise a server whose address changed before sign-in.ProgressGatehas no trailing publish for render-node reports.DESIGN.md§4 and the mockups (Jobs, Server, Admin, Archive, Settings, Uploader, setup) are not updated for the new screens.Refs #64 #65 #66 #67