3
Home
Sam Catlow edited this page 2026-10-11 14:43:36 +11:00

Archie development and release guide

This guide is the working plan for moving Archie into private development on Gitea and establishing reliable releases. The procedures described as planned still need implementation; they are not claims that the pipeline exists today.

The objective is a repeatable path from a selected commit to a verified installation. Computers build, install, test, collect evidence, and recover. Sam decides product scope, accepts known limitations, and approves deployment to production.

Start here

Work through these pages in order. Each has completion criteria so the next step starts from evidence.

  1. Finish the Gitea migration: establish the development checkout, private distribution, working runners, and the new release baseline.
  2. Set up project tracking: review the existing backlog and make Gitea the authoritative tracker.
  3. Build staging and QA: rehearse installation, upgrades, real workflows, and recovery.
  4. Implement the release process: build a candidate once, validate it, deploy it, and publish it as stable after verification.
  5. Define the first supported product release: set a useful, maintainable product boundary and earn the 1.0 designation.

The migration and tracking setup can progress together. A stable release depends on working private artifact distribution, staging QA, and production verification.

Decisions already made

Decision Direction
Development forge Private sam/archie on Gitea
Release numbering New 0.x series, beginning with 0.1.0
Product maturity 1.0.0 will represent a defined supported product
Project management Move from Beads to Gitea issues, milestones, and a project board
Release quality Validate the packaged artifacts in staging, then verify deployment
Automation Human approval; automated execution and evidence collection

Future licensing and commercial terms remain a separate decision. Repository privacy does not revoke the Apache 2.0 rights attached to previously published versions.

Current setup

Development is hosted in the private Gitea repository sam/archie, with main as the default branch. Commit history and branches are preserved. Historical release tags are excluded so the new 0.x release series can start independently.

  • Development checkout: /work/apps/archie-sha1, with origin pointing to Gitea.
  • Wiki checkout: /work/apps/archie.wiki.

Runner workflows, private distribution, project tracking, staging QA, and release automation still require implementation.

How to maintain this guide

Use Gitea issues for executable work and this wiki for the agreed process. Update repository instructions and RELEASING.md alongside implementation so agents and automation follow the same rules. When a process fails, fix the smallest concrete cause and update the relevant procedure.

A release is complete when the intended artifacts are running, the required QA passed, and the production checks passed. Publishing files alone does not meet that definition.