Process
Every piece of work is traceable: request, issue, branch, PR, commit, tag, release.
Flow
- Issue. One issue per work item or phase, with labels (
area/desktop, area/server, area/release, area/business, plus bug, enhancement, documentation, question) and a milestone.
- Branch. Work on a branch named after the phase (for example
or1-p6). The issue's branch reference points to it.
- Pull request. Description ends with
Closes #N. Commits refer to the issue (Refs #N).
- Squash merge into
main. The squash commit keeps the PR number.
- Tag
v0.1.0-rc.N on the merge commit; the release workflow builds installers, zips, SHA256SUMS and the server image.
- Release notes come from Conventional Commits. The milestone for that tag is closed with the release date.
Milestones
One per release (v0.1.0-rc.N, then v1.0.0). History is recorded: rc.1 to rc.13 are closed. A separate Licensing milestone holds parked licensing work.
Board
Project Road to 1.0: Backlog, To Do, In Progress, Done. Project Licensing: parked work for selling Chronos (issue #24).
Commits
Conventional Commits in English: feat:, fix:, docs:, test:, refactor:, build:, with ! for breaking changes.
CI checks (Gitea Actions)
- build and tests (Linux jobs; the Windows job when a Windows runner is registered)
Chronos.Tools package-guard: no package references
i18n check: every string in en and it
xaml-lint, pe-check
- visual baselines in
tests/visual/baselines
Definition of done per phase
CI green, tests green, no new warnings, DECISIONS and CHANGELOG updated, i18n check green, phase report with how to try it.
See also: CLAUDE.md and STATUS.