diff --git a/Directory.Build.props b/Directory.Build.props index 7fc1f73a..8891e980 100644 --- a/Directory.Build.props +++ b/Directory.Build.props @@ -1,7 +1,7 @@ $(MSBuildThisFileDirectory) - 0.1.0 + 1.0.0 $(ChronosVersion) $([System.Text.RegularExpressions.Regex]::Match($(ChronosVersion), '^\d+\.\d+\.\d+').Value).0 $(AssemblyVersion) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 1ec42556..3dc4ace2 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -5,6 +5,22 @@ commits follow Conventional Commits (release notes are generated from them by `C ## [Unreleased] +## [1.0.0] — 2026-11-06 + +The first stable release (owner review 3, R4; issue #23). It is the code of 0.1.0-rc.14. Upgrading from any 0.1.0 +pre-release keeps the archive, the database and the settings: migrations run at start (back up `/data` first, as +`docs/deploy/` says). + +### Changed +- Version 1.0.0: builds without a release tag now say 1.0.0. +- Update channels now follow stable releases only: + - The Docker image `chronos-server:latest` and the desktop update check move only with stable releases. + - A pre-release build is offered 1.0.0. + - Later pre-releases are installed by hand; their `:` image tags stay in the registry. +- On Unraid, set the template's Repository to `…/chronos-server:latest` if it still says `:nightly`. + +## [0.1.0-rc.14] — 2026-11-06 + ### Added - **Work board** (owner review 4, R1, #29): a third Videos layout, *Board*, on the desktop's Videos section and on the admin panel's Videos page: two lanes, *Published* and *Workspace*, newest first, each with its count, under the diff --git a/docs/DECISIONS.md b/docs/DECISIONS.md index 2f4d1dbc..b245908a 100644 --- a/docs/DECISIONS.md +++ b/docs/DECISIONS.md @@ -797,3 +797,4 @@ One line per decision: date · decision · alternative · reason. | 2026-11-06 | The admin board reads the server with `sort=newest` and disables *Order* with a tooltip; *Published* shows the server's total, *Workspace* the loaded count with "+" while a cursor remains; a Shift range runs along the lane picked in (`selectableGrid`'s `order(el)`). | Re-sort the loaded page; one range over every card | The board must show the server's newest renders and honest counts, and a range must cover only the cards seen between the two clicks (a sent render is in both lanes). | | 2026-11-06 | `CHRONOS_PARALLELISM` out of 1–64 stays clamped; the other range errors at start name the `CHRONOS_*` variable (`ServerOptions.VariableOf`). | Refuse every value out of range | Clamping parallelism is long-standing behaviour the admin panel relies on; the deploy guide documents the exception. | | 2026-11-06 | Desktop Board cards move their quick actions to a row under the text while the player pane is open. | Stack the lanes; hide the actions | Keeps both lanes side by side and every action on the card; at 1200 px with the player the text column grows from about 80 px to the whole card. | +| 2026-11-06 | `v1.0.0` is tagged on the code of `v0.1.0-rc.14` with no other change than the version (builds without a tag now say 1.0.0) | A last round of changes in 1.0.0 | Owner review 3 R4: finish everything, then the first stable release. rc.14 passed CI, its review and its release, so 1.0.0 ships what was tried; from here `:latest` and the update check follow stable releases only. | diff --git a/docs/STATUS.md b/docs/STATUS.md index c14baf60..1d0f0b60 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -17,7 +17,7 @@ by its `windows` job once a Windows runner is registered (`WINDOWS_RUNNER`), and | 8.1 Owner review 1 | In progress (request, answers and plan: `docs/requests/2026-10-15-owner-review-1.md`). Phase 1 done: stalled thumbnail and proxy jobs no longer fail and stay Running (frame-counted progress, bounded time left, final state always written); the editor's cancelled decodes stay in their tasks (no debugger stops in `WicDecoderProvider.cs`); WIC decodes RAW only through the Raw Image Extension and never DNG; GoPro DNGs converted by Adobe software are DNGs, developed natively for videos, read through their embedded preview for analyses and previews, and reclassified in existing archives by the next light analysis. Phase 2 done: jobs run one at a time on the desktop and the server; Parallelism is how many photos the running job processes at once (thumbnail and proxy passes, tier probes, deep analysis, render decodes); pausing the running job starts the next; an optional priority queue by job kind (Settings › Rendering, admin panel › Settings › Jobs, `CHRONOS_PRIORITY_QUEUE`) pauses lower jobs and resumes them by themselves; `CHRONOS_PARALLELISM` replaces `CHRONOS_WORKERS`. Phase 3a done: the rail is 200 px and collapses to icons with ≡ or Ctrl+B (tooltips then name the sections, the choice saved at once); the admin panel's sidebar is 256 px and collapses the same way. Phase 3b done: the Sequence section is now Edit, one sequence at a time chosen in a picker inside the section (Change sequence, Ctrl+O; the sequence edited last selected first), and the editor's tabs are the steps of a guided, freely navigable path from a new Analysis step (every finding with the step that deals with it) to Export, each step showing where it stands, with Previous and Next. Phase 4 done and released as `v0.1.0-rc.12` (issue #19, `188b2c2e`; one adversarial review round, 30 findings, all confirmed and fixed, and a final check that fixed one more; strings in all 38 languages; 31 screenshot baselines accepted): the crop edited on the preview with eight handles, always locked to the output's aspect, in the view frame, by mouse, keyboard (Enter selects) and Crop size/X/Y (R5); the chosen proportions win: a fixed-size preset is a box the aspect is fitted in (`RenderSize`: 4K at 9:16 = 2160×3840), "source" keeps the preset, *Output size* on the Export step; Rotation (quarter turns), Mirror, Flip and Straighten (±15°, automatic cover zoom, the grid while it moves) in the Camera step inside the one warp (`FrameOrientation`), a turn or mirror keeping the content (`OrientationEdit`: crop, keyframes, transposed aspect), Reset framing; eight built-in colour looks with a strength at the end of the Exposure step, after stacking and before the knee (`LookFilter`, `FrameFinish`), the same in the render, on the server, render nodes and the preview; settings format 2 written only while a transform or look is used (`ProjectSettings.RequiredFormat`), read-only in older builds; `server/info` and node registrations announce the settings format, jobs carry the one they need (`RenderRules.RequiredFormat`), and nothing an older server or node would get wrong is sent to it (Sync, Send and render, the Library's Render, a remote editor's save); encoder limits read either way round; the advisor on the view as shown. Also fixed on the way (issue #20): project text is LF on every OS, stored CRLF versions compare equal. Known limitations: an older desktop renders a chosen aspect at the preset's ratio on its own; the server's settings format is cached for a minute; the new Camera rows and the Straighten slider binding have no on-screen test. Phase 5 done, to be released as `v0.1.0-rc.13` (issue #21; eight parcels and an integration, one adversarial review round whose findings are all fixed; strings in English and Italian, the other 36 languages being imported): the header's *Render ▾* at a fixed width with its details in the tooltip and a structured menu (recommended, batch and recent presets, *Other presets ›* by group with a details line, *Render batch*, *Add to queue*, *Save frame ›*, *Videos*; `RenderMenu`, hierarchical two-line `SplitButton` entries) (R3); the Export step's grouped preset table, four collapsible groups with summaries kept per user (`ExportGroups`, `AppSettings.EditorGroups`) and a fixed footer (R3); advanced encoding (rate control, bit rate or quality, keyframes in seconds, B-frames, profile, gated per codec and depth) and standard resolutions over the existing overrides, no format raise (R8); playback (reverse, boomerang, loops, fades to black, hold) as the Core `OutputProgram` between the plan and the encoder, with estimates, progress and star trails following it, settings format 3 written only when used (R8); *Save frame* as a still render (PNG, JPEG, TIFF 16-bit; `RenderTarget.StillFrame`, `StillImageSession`; format-3 jobs, also from workspace projects) (R8); render SHA-256 and kind, render copies (migration 0010); the videos library (`VideoLibrary`, `VideoTrash` into `trash/videos/` with a dry run, fingerprint and journal, restore with the same id after a hash check; `VideoCopyJobHandler`, `video-copy` stored as 24, into a flat, hash-verified videos folder) on the desktop as the Videos section (Ctrl+4, Archive/Jobs/Server Ctrl+5…7; this PC's, the server's and unsent workspace renders merged, an in-process player) and on the server as `/api/v1/videos`, the `videos` capability, the admin panel's Videos page and the trash's Videos entries, `CHRONOS_VIDEOS_PATH` and the optional `/videos` volume (R9). Known limitations: GIF and APNG show their first frame in the desktop player; HEVC plays where Windows has its extension; older renders are hashed on first copy, delete or restore; the new screens have no screenshot scenes or baselines yet. Phase 6 in progress (issue #22), with owner review 4, for `v0.1.0-rc.14`: the deploy guide `docs/deploy/` (README, `docker.md` with every `CHRONOS_*` variable and its default, volumes, ports and public ports, TLS and the fingerprint, upgrades, backup and restore, PostgreSQL, troubleshooting; `unraid.md` with the owner's host ports 8087/8444 and Public HTTPS port 8444; `desktop.md` with Setup, portable mode and updates), BRIEF §14.9 (`CHRONOS_TRUSTED_PROXIES` listed), §19.6 and §24 (every amendment since owner review 1 listed); full verification before the release. Then `v1.0.0` (issue #23). | | 8.2 Chronos on Gitea | Done (request: `docs/requests/2026-10-23-chronos-gitea.md`): Titano renamed Chronos everywhere, translations' grammar included; repository, update check, links, issue forms and registry moved to the self-hosted Gitea; Gitea Actions CI, release, nightly image and performance workflows for the Linux runner, with the Windows programs cross-compiled and checked (`pe-check`); new `Chronos.Tools` commands `zip`, `gitea-release`, `postgres-ci`, `pe-check`. Pre-releases `v0.1.0-rc.1` and `v0.1.0-rc.2` (the update check builds its links from `ChronosReleasesUrl`, since Gitea's use its LAN ROOT_URL) published; `REGISTRY_TOKEN` is set and the `v0.1.0-rc.2` server image is in the registry. | | 8.3 Owner review 2 | Done (request, answers and plan: `docs/requests/2026-10-26-owner-review-2.md`). Phase 1 done and released as `v0.1.0-rc.3` (one adversarial review round, 19 findings fixed; strings in all 38 languages): `:latest` follows the highest stable release, or the highest pre-release while none is stable (`Chronos.Tools release-channels`), `:nightly` stays the nightly build of `main` (R1); `CHRONOS_SPACE_PATH` and the Unraid template's *Array view* (`/mnt/user0/` read-only at `/space`) make the admin panel show the array's free space, the cache apart as *Write volume*, the file system in the tooltip, and completing an upload checks the archive volume first (507, resumable) (R2); the Settings icon is a toothed gear and the admin panel docks Settings at the foot of its sidebar (R4); About is the last page of Settings on the desktop and the last group of Settings on the admin panel (R5); Import › Folder… › *Whole folder* imports a folder as one sequence per format, titled after the folder (R9). Phase 2 done and released as `v0.1.0-rc.4` (one adversarial review round, 35 findings fixed; strings in all 38 languages): scheduled jobs (R10) — schedules (migration 0007) with an in-house recurrence form, one scheduler per host claiming runs by compare-and-set with catch-up, and Jobs › Scheduled on the desktop and the admin panel (`/api/v1/schedules`, `scheduleChanged`); every timer that queued work is a visible system schedule (server: archive scan, upload clean-up every 6 h, index backup at 03:00, job history and audit log clean-ups; desktop: archive scan, daily index backup, housekeeping with cache trim), the archive still scanned at start; new Backup and Clean-up jobs, duplicates and orphans reports as jobs, one backup retention, the trash only reported; log settings (R11) — file and console levels, retention, file and total size limits, daily or hourly rotation, audit retention (the audit clean-up schedule's) and the diagnostics share in the admin panel's Settings › Logs (`CHRONOS_LOG_*`, `lockedBy`) and the desktop's Settings › Advanced; the server's files take Debug and Trace again, and logging never fails a job. Phase 3 done and released as `v0.1.0-rc.5` (one adversarial review round and two fix rounds, 40 findings fixed; strings in all 38 languages; Library, photo delete and restore and the web upload tried by hand): the admin panel manages and never edits (R6) — a Library page (facets filters, cards or list, keyboard selection, mass Analyse, Proxies, Thumbnails, Verify, Tags, Export CSV and Delete, 1,000 sequences a request), a sequence's page (inline title, tags, rating, notes, photo viewer, cover, downloads, photo delete) and the trash view (Restore, Empty… behind a dry run, the typed word and a fingerprint); photos deleted into `trash/photos` under crash-safe journals with tombstones in the sidecar and `frame_removals` (migration 0008), so sync and uploads never bring them back unless restored or uploaded again on purpose; trash kinds, restore reasons and the `EmptyTrash` job on the desktop's Trash… too (typed entry count); the panel's files revalidated (`no-cache`, ETag); upload from the panel (R3) — file picker or drop, no folders, a self-tested in-house SHA-256 in a module worker, Exif capture time, resumable chunks. Known limitations: a never-hashed photo whose file was already missing is deleted without a tombstone; an unhashed server frame of a photo deleted on a PC stays *missing here* until the server verifies it; `jobState` carries no kind, so panel pages refresh after any job. Phase 4a done and released as `v0.1.0-rc.6` (one adversarial review round and six fix rounds; strings in all 38 languages): Reorganize after import (R7) on the desktop (Archive manager, Library, the toast after Settings › Archive templates change; it replaces Rename… and Move…) and the admin panel (Library, the *Saved* toast of Archive) — folder, file and title templates applied to filed sequences behind a dry run that lists every change, the photos that keep their names and why (in place, never verified, missing) and the sequences that stay whole (unreadable sidecar), applied by the `move` job of exactly the confirmed plan (fingerprint, `POST /api/v1/archive/reorganize`, plans kept a few minutes on the server), which holds the rest when paused, cancelled or failed (also while the archive is offline), lets a sequence still receiving photos keep its file names and takes along a sequence left as it was inside a folder that moves; files renamed in two phases under `.chronos/rename-files.json`, completed after a crash by the next writer; the index, frames and exports follow a moved folder in one transaction, here and at another index's next scan, and writers never create a folder a Reorganize left nor write into one another sequence took; import, upload and Reorganize name photos by one rule (the sequence's camera and lens), and templates follow one set of rules everywhere (no folder scans skip, the extension kept, names that tell photos apart), held only to templates given anew. Known limitations: a reader without the sequence's lease can miss a file while its files are renamed; a change made on disk alone after a server dry run is found by the job, which fails changing nothing; a photo restored from the trash after a Reorganize keeps its old name; a render of another program whose folder moves while it runs is not stopped. Phase 4b done and released as `v0.1.0-rc.7` (one adversarial review round, 42 findings, and three fix rounds; strings in all 38 languages): mass conversion after import (R7) on the desktop (the Archive manager's set, the Library's selection) and the admin panel (the Library's selection) — JPEG with a quality, TIFF-16 or linear DNG (the archival choice, scene-referred so a RAW's highlights above white and colours outside sRGB survive), Replace or New sequence chosen at every run and never remembered, behind a dry run that lists each sequence's photos and sizes, the photos that stay as they are and why (on the server, what it cannot read at full resolution: convert on a PC) and the free space where the conversion writes; Replace confirmed by typing; the `convert` job (stored as 19) converts exactly the photos confirmed (their digest in its parameters, their ids in `journal/convert-.photos`, pinned when it first comes to a sequence; a retried New sequence never makes a second copy), one sequence at a time and all or nothing, resumable through `journal/convert-.*` and `staging/convert-/`, never twice at once; full-resolution decodes with the managed decoders first (never a 16-bit file from an 8-bit RAW development, never a TIFF WIC would read as black or noise), what Chronos reads from a photo never changed (a JPEG or TIFF-16 carries the profile; a linear DNG takes sRGB values only, so Adobe RGB, Display P3, ProPhoto and gamma-1.0 photos go to TIFF-16 or JPEG), Exif carried, every file verified by the server's decoders; Replace swaps the files of the frames in place under `replace.pending.json`, the originals going into a replaced trash entry that the toast's Undo or Restore swaps back and that Empty erases only while the archive on disk shows each conversion intact, or deleted on its own word (a tombstone, the trash, or `trash/.erased/.json`; named first in its confirmation); import still copies byte for byte and the card keeps a converted photo's copy; sync and the ingest count every encoding of a photo as one; `POST /api/v1/archive/convert` in the plan cache Reorganize uses. Known limitations: a photo that fails although its headers read well leaves its sequence as it was; a decode larger than the memory stops the job; a damaged file that still decodes converts as decoded; a read error while a dry run reads a TIFF, DNG or TIFF-based RAW header lists the photo as needing a PC, preview-only or unreadable rather than held (the reader swallows it; nothing beyond the plan converts); JPEG and TIFF-16 clip float values beyond 0..1; not verified: a TIFF whose first image is a thumbnail and whose main image only WIC reads would convert at the thumbnail's size; a PNG's gamma and primaries without a profile count as sRGB; a linear DNG bakes the white balance in and clips below black; the desktop's Undo lives in the job's end toast only (later: Restore). Phase 5a done and released as `v0.1.0-rc.8` (one adversarial review round, 55 findings, and five fix rounds; strings in en and it): the desktop's workspace and projects with this PC's archive as the home (R8) — a sequence's projects (Main, mirrored both ways with the sequence's settings so older clients, analyses and sync keep working, and other named projects), each a linear history of immutable versions in the portable form (positions parked by photo, SHA-256 of canonical text), kept as sidecars in `.chronos/projects/` and indexed by migration 0009 (`projects`, `project_versions`, `renders.project_id`/`project_version_id`), deleted only on the archive's word (the projects' trash read first), healed from the index when a record is lost or behind, one Main decided from the records; Edit opens only workspace projects: *Open in workspace* (project, proxies, copy size and free space), the `workspace-copy` job (stored as 20, desktop only, hash-verified, resumable, space checked, its cancel clean-up under the project's lease), the working state in a folder outside the library, the title's project button (state chip; Save version with Ctrl+S, Sync, History with Compare and Restore, Open, New, Rename, Delete, Remove local copy after a plan), push and pull with replay and field-level merge under crash-safe journals, conflicts only where both sides changed a setting (Keep mine, Take library's, Save both, Later), Update media, newer and damaged copies named and left untouched, renders at the home with the settings embedded, `.chronos` format 2; Settings › Workspace (Folder with Change…, Sync, Kept versions). Known limitations: a server sequence still opens with proxies (the server home is 5b); originals, local render, moving the folder with its projects, emptying `/.trash`, clean-up and the size limit are 5c; a capture still edits the library; nothing restores from the projects' trash yet; a lost record waits 2 minutes of one running Chronos before it is written again. Phase 5b done and released as `v0.1.0-rc.10` on 2026-11-04 (`81c303f4`; one adversarial review round, 21 findings, 19 fixed; strings in all 38 languages): a Chronos Server as the home of its sequences' projects (R8) — `/api/v1/sequences/{sid}/projects` on the archive's `ProjectService` (list with Main made at the first read, create, rename, delete by the owner, the maker or an admin, head, versions in size-capped pages, the stored check, push with its outcome, the frames and their stamp), the `projects` capability and `projectChanged`, Main taking settings written outside the projects soon after (`ProjectCatchUp`), a settings `PATCH` writing `project.json` under the lease, no projects for a sequence without photos, renders and render nodes of a project version, and the admin panel's Projects section (versions, Rename, Delete); on the desktop `ServerProjectHome` through the signed-in session: *Open in workspace* in Edit and on the Server screen, the proxies downloaded into the workspace (hash-checked, resumable, thumbnails standing in while the server has no proxy), push, pull, conflicts, history and the chip against the server (*Server newer*, *Not on server*), renames followed, renders and analyses on the server of the version it holds after *Send and render*; an account without Edit and an older server keep *Open with proxies*. Known limitations: projects read *Offline* when signed in to their server through another address; a copy reads the server's frames in one answer; *History* downloads every version's settings. A final check (2026-11-04) fixed what it left: Main's birth on an upgraded server keeps the settings an earlier release's `PATCH` wrote into the index alone (`IndexSettingsMayLead`), a pull never fails on the name it follows, the Server screen's row actions stay on one line and the capture shows sample paths (16 baselines recaptured: `server-*`, `settings-storage`, `settings-workspace`, `settings-advanced`, `archive-rebuild`). Phase 5c done and released as `v0.1.0-rc.11` on 2026-11-04 (`db389a54`; one adversarial review round, 35 findings, 32 confirmed and fixed, compat-2 in part; a final check fixed one more; strings in all 38 languages): originals in the workspace (R8) — *Open in workspace* › *Originals* (Default media first; sizes also for a server's sequence), *Copy originals…* and *Proxies only…* behind a plan, the copy from either home streamed, hash-checked against the home and resumable, a frame without a usable original keeping its proxy, media index format 2 and project file format 3 while originals are held (older Chronos refuses them); local render (`workspace-render`, stored as 21) from the workspace's originals into `exports/` with the ledger `renders.json`, *Version on render* saving a version first, and *Send render* (`workspace-send`, 22) to this PC's archive (staged, read back, filed under the lease) or to the server (`RenderUploadRequest` with `projectId`/`projectVersionId`, checked against the sequence, 422 `project_mismatch`), idempotent by render id, refusals per render, a version a replay renamed found by its content hash, the Export step's *Not sent* and *Send again*; *Pause metered transfers* holding uploads, the sync's downloads and the workspace's server copies and sends; originals judged by their bytes against the home's frames on removal, clean-up and Proxies only, the rest kept in the workspace's trash (entries filled under `.incoming-` names, emptied only by *Empty…* with the entry count typed and a fingerprint); the clean-up (`WorkspaceCleaner`: projects in step with their home, not open, without jobs or unsent renders; *Clean after* 30 days and *Size limit* 100 GB, the `workspace-cleanup` schedule daily at 04:30 and the limit after each copy); Remove local copy weighing unsent renders and originals; moving the workspace folder (`workspace-move`, 23; `WorkspaceMover`): a plan, renamed on one volume or copied and hash-verified across volumes, the journal `.move.json`, the source kept until the switch, resume and undo, jobs finding their project where the workspace is now (`WorkspaceJobRoots`), *Resume* in Settings; Settings › Workspace complete (Folder with Move…, Size limit, Default media, Sync, Version on render, Kept versions, Clean after, Open project, Trash). Known limitations: an older server drops a render's provenance and the render is still marked sent (logged); an original held open after Proxies only leaves the media index at format 1, so a downgraded 0.1.0-rc.10 could delete it; the removal plan's original count is an estimate and can fail when `media/originals` cannot be read; the Export tab's *Send again* view model has no unit test. | -| 8.4 Owner review 4 | In progress (request and plan: `docs/requests/2026-11-06-owner-review-4.md`), one phase released as `v0.1.0-rc.14` with owner review 1 phase 6, then `v1.0.0` (#23): R1 work board of every video made or published, the published apart from workspace work (#29); R2 the anonymous usage counts removed, nothing sent by itself (#30); R3 the archive's whole folder structure created inside the chosen archive path, desktop and server (#31); R4 the repository on Gitea in order (earlier work as closed issues #32–#54 in their milestones, the original documentation in `docs/reference/original`, `fe50b877`); R5 licensing set aside and recorded in #24. Work stops at 75% of the weekly usage. | +| 8.4 Owner review 4 | Done (request and plan: `docs/requests/2026-11-06-owner-review-4.md`): released as `v0.1.0-rc.14` with owner review 1 phase 6 (the deploy guide `docs/deploy/`), then as `v1.0.0` (#23), the first stable release: R1 work board of every video made or published, the published apart from workspace work (#29); R2 the anonymous usage counts removed, nothing sent by itself (#30); R3 the archive's whole folder structure created inside the chosen archive path, desktop and server (#31); R4 the repository on Gitea in order (earlier work as closed issues #32–#54 in their milestones, the original documentation in `docs/reference/original`, `fe50b877`); R5 licensing set aside and recorded in #24. | | 9 Monetization | Not started: requires explicit approval (§22); the proposal is recorded in issue #24 (owner review 4, R5). | ## Verification (2026-10-12) @@ -160,26 +160,22 @@ src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshot ## Next steps -Each phase ends with a release (owner review 2, R12): - -1. Owner review 4 with owner review 1 phase 6 (issues #29, #30, #31, #22, #28): the work board, the usage counts - removed, the archive's folder structure, the deploy guide (`docs/deploy/`) and BRIEF §24; released as - `v0.1.0-rc.14`. -2. `v1.0.0` (issue #23), the first stable release (owner review 3, R4): `:latest` then follows stable releases only, - and the update check offers it to every pre-release build. +`v1.0.0` is released: `:latest` and the update check now follow stable releases only. Later work gets its issue and +milestone on Gitea (board *Road to 1.0*; licensing on the board *Licensing*, issues #55–#61, waiting for the owner's +approval of Phase 9). Phase 8 gate: -3. Visibility: make the `BalboSoft` organisation (and its packages) public, or publish to a public `RELEASES_REPO`, so +1. Visibility: make the `BalboSoft` organisation (and its packages) public, or publish to a public `RELEASES_REPO`, so that people without an account can download releases, get update notices and pull the image. -4. Windows runner: register an act_runner in host mode on a Windows PC (.NET SDK, Git for Windows, PowerShell 7) and +2. Windows runner: register an act_runner in host mode on a Windows PC (.NET SDK, Git for Windows, PowerShell 7) and set the repository variable `WINDOWS_RUNNER` to its label. The screenshot baselines in `tests/visual/baselines` were captured on the development PC (2026-11-04): register the runner on that PC, or accept a new set captured on the runner's PC (its README says how). From then on a visual change, or a screen without a baseline, fails the `windows` job. -5. On Windows: install the latest pre-release's setup, upgrade over the previous version, uninstall (with and without +3. On Windows: install the latest pre-release's setup, upgrade over the previous version, uninstall (with and without user data), silent mode. -6. Unraid: install the template as a user template (README › Server image, Compose and Unraid) with the official +4. Unraid: install the template as a user template (README › Server image, Compose and Unraid) with the official PostgreSQL template, check that its icon (the SVG of `branding/`) shows, reach the WebUI, and that the Dashboard shows the array's free space through *Array view*. -7. Native-speaker review of the machine translations where users report wording (`i18n export` per language). +5. Native-speaker review of the machine translations where users report wording (`i18n export` per language). diff --git a/docs/requests/2026-11-04-owner-review-3.md b/docs/requests/2026-11-04-owner-review-3.md index df1ebe8a..e79ef65d 100644 --- a/docs/requests/2026-11-04-owner-review-3.md +++ b/docs/requests/2026-11-04-owner-review-3.md @@ -44,4 +44,4 @@ Two screenshots came with it: the Unraid template (repository `chronos-server:ni |---|---|---|---| | 1 | R1 ports, R2 baselines | done 2026-11-04, released as `v0.1.0-rc.9` (one review round with two reviewers and a checker; strings in all 38 languages): BRIEF §12.7, §14.8, §14.9, §19.6; DECISIONS rows dated 2026-11-04 (public ports as settings, the settings DTO members, the container port lock, saved listening ports removed, the client address, one address rule, the Chronos identity checks, the HTTP port typed as HTTPS, the zone index, Host networking, baselines from the development PC, fixed capture values); CHANGELOG [Unreleased] with the Unraid upgrade note | `255e1490` | | 2 | R4 owner review 2 phases 5b and 5c | done 2026-11-04: 5b released as `v0.1.0-rc.10` (`81c303f4`), 5c as `v0.1.0-rc.11` (`db389a54`) | `81c303f4` (5b), `db389a54` (5c) | -| 3 | R4 owner review 1 phases 4–6, then `v1.0.0` | in progress: phase 4 done 2026-11-04, released as `v0.1.0-rc.12` (issue #19, `188b2c2e`); phase 5 done 2026-11-05, to be released as `v0.1.0-rc.13` (issue #21); phase 6 (#22) in progress for `v0.1.0-rc.14` with owner review 4 (2026-11-06); `v1.0.0` (#23) todo | `188b2c2e` (phase 4) | +| 3 | R4 owner review 1 phases 4–6, then `v1.0.0` | done 2026-11-06: phase 4 released as `v0.1.0-rc.12` (issue #19, `188b2c2e`), phase 5 as `v0.1.0-rc.13` (issue #21, `728ffa35`), phase 6 with owner review 4 as `v0.1.0-rc.14` (issue #22, `00750658`); `v1.0.0` (#23) released on 2026-11-06 | `188b2c2e`, `728ffa35`, `00750658` | diff --git a/docs/requests/2026-11-06-owner-review-4.md b/docs/requests/2026-11-06-owner-review-4.md index eed05231..352feac2 100644 --- a/docs/requests/2026-11-06-owner-review-4.md +++ b/docs/requests/2026-11-06-owner-review-4.md @@ -40,5 +40,5 @@ The owner corrects an interpretation at the next review. | Phase | Content | State | Commit | |---|---|---|---| -| 1 | R1 work board (#29), R2 usage counts removed (#30), R3 archive folder structure (#31); R4 repository; R5 #24; owner review 1 phase 6 (#22): `docs/deploy/` (Docker, Unraid, desktop), BRIEF §14.9, §19.6, §24 | in progress, to be released as `v0.1.0-rc.14` | | -| 2 | `v1.0.0` (#23), the first stable release (owner review 3, R4) | todo | | +| 1 | R1 work board (#29), R2 usage counts removed (#30), R3 archive folder structure (#31); R4 repository; R5 #24; owner review 1 phase 6 (#22): `docs/deploy/` (Docker, Unraid, desktop), BRIEF §14.9, §19.6, §24 | done 2026-11-06, released as `v0.1.0-rc.14` (PR #62; one review round, 10 findings fixed; strings in all 38 languages) | `00750658` | +| 2 | `v1.0.0` (#23), the first stable release (owner review 3, R4) | done 2026-11-06, released as `v1.0.0` | | diff --git a/tests/visual/baselines/settings-about-dark.png b/tests/visual/baselines/settings-about-dark.png index 5b64e6d3..79a47725 100644 Binary files a/tests/visual/baselines/settings-about-dark.png and b/tests/visual/baselines/settings-about-dark.png differ diff --git a/tests/visual/baselines/settings-about-light.png b/tests/visual/baselines/settings-about-light.png index 3ebaa340..e49471b9 100644 Binary files a/tests/visual/baselines/settings-about-light.png and b/tests/visual/baselines/settings-about-light.png differ