Rewrite the release procedure for the Actions pipeline The old procedure described the Jenkins buildfarm and required being on a particular corporate network. Building and publishing now run on GitHub Actions, so anyone with write access to the repository can do it. What changed beyond the job names: candidates test themselves, so there is an explicit statement that a red acceptance test means a new candidate rather than a repair; promotion takes a scope, so the steps that cannot be undone are named as such; and the container images and Helm chart are flagged as still running from Jenkins. Also adds an index page.
Initial Home page