Release process » History » Version 5
Elijah Young, 06/19/2026 07:42 PM
Minor update
| 1 | 1 | Sara Haddad | h1. Release process |
|---|---|---|---|
| 2 | |||
| 3 | h2. Schedule |
||
| 4 | |||
| 5 | Planned releases are listed in the *Roadmap* tab. Hotfixes can go out any weekday before 16:00. |
||
| 6 | |||
| 7 | h2. Steps |
||
| 8 | |||
| 9 | # Freeze the scope: only fixes after the release candidate. |
||
| 10 | # QA runs the regression suite on the release candidate. |
||
| 11 | # DevOps deploys with the blue-green pipeline. |
||
| 12 | # Monitor error rate and latency for 30 minutes. |
||
| 13 | # Publish the release notes and close the version. |
||
| 14 | |||
| 15 | h2. Rollback |
||
| 16 | |||
| 17 | Switch the traffic back to the previous environment; database migrations are written to be backward compatible for one release. |
||
| 18 | 3 | Sophia Bianchi | |
| 19 | |||
| 20 | * Update 2026-06-01: Started working on it, will post an update after the first run. |
||
| 21 | 5 | Elijah Young | |
| 22 | * Update 2026-06-19: Reproduced the problem; the cause is in the data migration. |
