Devlog #19: Our release process

Every Quedula release goes through the same path. We made it deliberately predictable.

Before a release: all planned changes in a branch, tests pass, changelog is written. No "quick fixes directly in prod."

We choose the release moment deliberately — not Friday evening, not a day when the team has low bandwidth. If something goes wrong, you need to be ready to respond.

After the release: we watch key metrics for the first few hours. If we see anomalies — we know how to roll back.

A boring, predictable process is a good thing. Surprises in releases are not needed.