Changes
Comparing empty → 123ce8e.
| @@ -1,0 +1,22 @@ | ||
| 1 | +--- | |
| 2 | +title: Friday-afternoon shipping window — opt-out next sprint | |
| 3 | +sort: 99999530 | |
| 4 | +tags: [process] | |
| 5 | +author: Pavel Stoyanov | |
| 6 | +--- | |
| 7 | + | |
| 8 | +# Friday-afternoon shipping window — opt-out next sprint | |
| 9 | + | |
| 10 | +The "no deploys after 14:00 Friday" rule has been in place for two years. It catches a real class | |
| 11 | +of weekend incidents, but it also burns Friday afternoons for teams that ship low-risk PRs. | |
| 12 | + | |
| 13 | +Starting next sprint, the policy becomes opt-in per service: | |
| 14 | + | |
| 15 | +- Default behaviour is unchanged — the deploy pipeline blocks production deploys after 14:00 local. | |
| 16 | +- A service can opt out by adding `friday_afternoon_deploys: allowed` to its `service.yaml`. | |
| 17 | +- Opting out requires the owning EM's signoff (the file enforces an EM-only CODEOWNER for that key). | |
| 18 | + | |
| 19 | +Two reasons we're loosening it now: trunk-based CI catches regressions earlier than it did in 2024, | |
| 20 | +and the on-call rotation has full APAC coverage so a Friday deploy isn't a EU-only burden. | |
| 21 | + | |
| 22 | +If your team wants to opt out, the PR template is in `runbooks/opt-out-friday.md`. | |