Road to the first supported product release
Guide home · Previous: release process
The historical 1.53.0 numbering records development releases. The new 0.x series will make product maturity explicit. 1.0.0 should represent a product promise Sam can maintain.
Define the supported boundary
Write down the first supported installation method, operating system/architecture, required dependencies, supported providers/channels, and the workflows a user can rely on. Confirm these against behaviour in the running system.
Choose the smallest useful complete product. Finish features within that boundary, remove dead paths, and document real limitations. Avoid delaying 1.0 for unrelated capabilities outside the promised scope.
The external contract includes user-visible settings, workflow behaviour, APIs, data persistence, and supported upgrade behaviour. Define which parts are stable and what constitutes a breaking change. Product versions and database migration identifiers have different purposes.
Proposed milestones
| Milestone | Outcome |
|---|---|
| Private development | Gitea checkout, reviewed issue backlog, runner gate, authenticated private distribution |
| Release rehearsal | Repeatable staging with installation, upgrade, representative workflow, and recovery evidence |
0.1.0 |
First candidate delivered and verified through the new private release process |
Subsequent 0.x releases |
Close observed product gaps and demonstrate repeatable upgrades |
1.0.0 |
Defined supported product boundary and release criteria met |
These are outcomes, not invented deadlines. Set dates after estimating the reviewed work and identifying real dependencies.
1.0 acceptance criteria
- A documented supported installation can be provisioned from scratch through automation.
- The promised user workflows work end to end, including real provider and agent execution paths.
- Settings exposed to users have functioning consumers.
- Service failures stay local and accepted work survives restart or dependency absence.
- Security boundaries remain intact, including grants, secrets, HMAC verification, and container confinement.
- A supported previous release can upgrade with its data and configuration preserved.
- Recovery is rehearsed, with explicit handling of schema changes and accepted work.
- The release pipeline deploys the exact staged artifacts and records production verification.
- Installation, operation, update, and troubleshooting documentation describe actual behaviour.
- Sam has decided the commercial offering and future licensing terms before distributing a commercial release.
Use existing checks and real acceptance scenarios as evidence. Add tests for actual regressions or important changed contracts rather than creating a large suite of assertions about wiring.
Commercial decisions still open
Decide who the first customer is, what they buy, the deployment responsibility, support scope, and the terms for future development. These decisions determine the operational promise; repository size and development cost alone do not define that promise.
Previously published Apache 2.0 versions retain their granted rights. Any change to future terms needs a review of contribution ownership and included dependencies. The migration did not change the licence.
The release work can progress while these decisions are being made. A dependable private deployment and upgrade process is useful regardless of the eventual commercial model.