docs: changelog and status for 0.1.0-rc.2 #8
No files matched your search
@@ -5,6 +5,8 @@ commits follow Conventional Commits (release notes are generated from them by `C
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
## [0.1.0-rc.2] — 2026-10-23
|
||||
|
||||
### Fixed
|
||||
- Update check: the release page and the download links come from the repository address the build names
|
||||
(`ChronosReleasesUrl`), not from Gitea's answer, whose links use Gitea's ROOT_URL; with the owner's plain-http LAN
|
||||
|
||||
+3
-3
@@ -15,7 +15,7 @@ by its `windows` job once a Windows runner is registered (`WINDOWS_RUNNER`), and
|
||||
| 7 Server, sync, uploader | Done: server (API, auth, uploads, jobs, render nodes, events, admin panel with light and dark themes, Windows service), Uploader, client sync (sync table, conflicts with *Save both*, proxies kept offline, metered pause), server sequences edited with proxies and rendered where the originals are, this PC as a render node. Gate covered in-process: a sequence uploaded from one PC downloads identically on another, interrupted uploads and downloads resume, server events update a PC, renders run on a node and on the server's managed fallback, jobs resume after a restart, sign-ins and administrative actions are audited. The run with two real PCs and the Uploader against the Docker server is part of the release test. |
|
||||
| 8 Release readiness | Release pipeline end to end (installers, portable and server zips, SHA256SUMS, release notes, optional signing, server image in the Gitea container registry, optional separate releases repository), update check with verified download, scrubbed diagnostics bundles (desktop and server), performance gates, 38 cultures (`en`, `it` and 36 machine translations with glossaries and independent reviews), RTL pass (`ar`, `he`: mirrored windows, left-to-right islands for media, charts, numbers and paths; any right-to-left culture added later follows), accessibility pass (names, live regions, keyboard paths for charts and the curve editor). The installer test (silent install of the packed installers, run, upgrade in place, uninstall: files, Add/Remove Programs, shortcuts, file type, user data kept, exit codes) runs in CI's `windows` job on a Windows runner. Pending: the interactive install on a real PC, Unraid template validation on a real server. |
|
||||
| 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. Next: phase 4, the visual crop locked to the output's proportions (R5) and mirroring, 90° rotations, straightening and colour filters (R6). |
|
||||
| 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`. First pre-release `v0.1.0-rc.1` tagged; its server image waits for the `REGISTRY_TOKEN` secret. |
|
||||
| 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; their server images wait for the `REGISTRY_TOKEN` secret. |
|
||||
| 9 Monetization | Not started: requires explicit approval (§22). |
|
||||
|
||||
## Verification (2026-10-12)
|
||||
@@ -68,7 +68,7 @@ src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshot
|
||||
## Next steps (Phase 8 gate)
|
||||
|
||||
1. Server image: create an access token with *package: read and write*, save it as the repository secret
|
||||
`REGISTRY_TOKEN`, then re-run the *Server image* job of the `v0.1.0-rc.1` release run (Actions › Release).
|
||||
`REGISTRY_TOKEN`, then re-run the *Server image* job of the `v0.1.0-rc.2` release run (Actions › Release).
|
||||
2. 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.
|
||||
3. Windows runner: register an act_runner in host mode on a Windows PC (.NET SDK, Git for Windows, PowerShell 7) and set
|
||||
@@ -76,7 +76,7 @@ src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshot
|
||||
of the first green `windows` job of a pull request, run `dotnet run --project src/Chronos.Tools -- screenshots accept
|
||||
<dir>` and commit the PNGs to `tests/visual/baselines` (its README says how). From then on a visual change, or a
|
||||
screen without a baseline, fails the `windows` job.
|
||||
4. On Windows: install the `v0.1.0-rc.1` setup, upgrade over the previous version, uninstall (with and without user
|
||||
4. On Windows: install the `v0.1.0-rc.2` setup, upgrade over the previous version, uninstall (with and without user
|
||||
data), silent mode.
|
||||
5. 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.
|
||||
|
||||
@@ -48,4 +48,5 @@ Nothing blocked the work; these need the owner because they are the owner's sett
|
||||
| Phase | State | Commit | BRIEF | DECISIONS |
|
||||
|---|---|---|---|---|
|
||||
| R1 rename, R2 Gitea references, R3 workflows and tools | Done | `refactor!: rename Titano to Chronos and move CI and releases to Gitea` | §0.2, §3, §16, §18, §19, §20.2, §21, §22, §23, §24, Appendix A | rows dated 2026-10-23 |
|
||||
| First release `v0.1.0-rc.1` | Tagged after the merge into `main`; the server image waits for `REGISTRY_TOKEN` | — | — | — |
|
||||
| First release `v0.1.0-rc.1` | Published after the merge into `main`; the server image waits for `REGISTRY_TOKEN` | `refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)` | — | — |
|
||||
| Update links, `v0.1.0-rc.2` | Published: the update check builds its links from `ChronosReleasesUrl` (Gitea's use its LAN ROOT_URL); the server image waits for `REGISTRY_TOKEN` | `fix(app): build update links from the releases repository address (#7)` | §18 | row dated 2026-10-23 (update links) |
|
||||
Reference in new issue
Block a user