What shipping looks like on a three-person team
In late October, ArbeitszeitCheck shipped five releases in ten days. That cadence is the answer to "how does a team this small ship this much", so here's what that stretch actually looked like, mechanics included, because the polished version would skip everything that makes it true.
Tuesday: three releases, one date
Three of those releases carry the same date. That isn't a changelog typo; it's what the packaging pipeline looks like when the smoke test catches something while you're signing the build that fixed the thing the previous smoke test caught. You don't ship the half-fixed version and promise a follow-up, you repackage, re-sign, and the changelog gets three entries instead of one dishonest one.
This is the part nobody sees from the outside: the version number in the App Store is the visible tip of a chain of "build, verify, notice, fix, rebuild." A three-person team can move that chain fast precisely because there's no release manager, no sign-off board, no sprint boundary between the fix and the package. The person who wrote the fix is the person signing the build.
The unglamorous machinery behind it
What makes same-day turnaround survivable is machinery, not heroics. Migrations are written so an organisation jumping five versions lands safely, skipping intermediate releases is normal admin behaviour, so we treat it as the primary case, not the exception. Repair steps fix data in place rather than asking admins to re-enter it. Changelog entries are written in the language an admin reads at 11 p.m., which means they say what changed and what to check, not what we wish had changed.
And anything not finished goes behind a "planned" label or doesn't ship. Half-finished features in a released app are how you harvest support tickets written by confused admins, and we don't have a support desk to absorb them, which is a feature of the process, not a complaint about it.
Release day is paperwork: the good kind
Tag, changelog entry, build, sign, publish. The Nextcloud App Store picks up the package; the mobile companions go through their own store reviews at whatever pace Apple and Google find appropriate that week, which is its own kind of entertainment: a release can be live for every self-hosted admin while the companion build still sits in review because a permission description needs a comma moved.
The asymmetry is worth naming. Server releases ship the moment the build is signed, your instance, your timing. Companion releases ship when a store reviewer says so. If you ever wondered why the web app is the centre of the product and the companions orbit it, this is part of the reason.
What the count doesn't tell you
More than five hundred releases sit in the changelogs behind our release notes. The number matters less than the shape: small releases, plain-language changelogs, fixes that go from report to signed package in days because there's no queue for them to wait in.
That is the whole answer to the question, really, not velocity as a virtue, but no distance between the person who writes the fix and the person who ships it.