One manual per company. Each keeps its own revisions, copy holders and distribution register.
Clients never install anything: they are always on whatever is deployed to live. This page sets how often that happens, and records what has gone out.
| Step | What happens |
|---|---|
| 1. Build | Changes are made and tested on the development copy. Clients see nothing. |
| 2. Staging | git push origin main
deploys to the staging copy — same code, its own database. The tests run
first, and nothing restarts if they fail. |
| 3. Try it | Use staging as a client would. This is the only step that cannot be automated. |
| 4. Release | git push origin main:live.
Every database is backed up first, then live restarts on the new version. |
| If it goes wrong | git push origin
<previous>:live --force puts the old version back. |
The schedule below is a reminder, not a trigger. Nothing deploys on its own — a release is always a decision you make after looking at staging. Security fixes and anything that loses data go out the same day, whatever the schedule says.
Once a month means the first chosen weekday of the month — "the 1st" drifts across the week and lands on weekends. Every two weeks counts from the last live release, so a skipped slot does not reset the rhythm.