Stable · candidate · beta · edge
Release Channels
The datab-app snap publishes to four channels. The channel an institution tracks decides how aggressive its update cadence is.
| Channel | Audience | Update cadence |
|---|---|---|
| stable | Production institutions. | Promotion from candidate after a soak window. Lowest churn. |
| candidate | RC1 is here. Pilot institutions + Datab-internal nodes. | Per-release cuts. Tested but not yet long-soaked. |
| beta | Partner labs + Datab engineering nodes. | Weekly or per-feature. |
| edge | Datab engineering only. Never run in production. | Continuous. |
Switching channels
# View the current tracking channel snap info datab-app | grep tracking # Move to a specific channel sudo snap refresh --channel=candidate datab-app # Hold updates for 24 hours sudo snap refresh --hold=24h datab-app
Don't downgrade silently
Moving from stable to edge is reversible but exposes the node to bleeding-edge changes that include unfinished security work. The downgrade runbook documents the process: see snap-channel-downgrade.md.