On this page
We ship Ferrybox every two weeks. Not "roughly every two weeks" – every second Tuesday, with a changelog entry for each change. Here's how the rhythm works and why we stick to it.
Why two weeks#
We tried weekly releases first. They were too short for anything substantial, so bigger features lived on long-running branches and arrived in large, risky drops. Monthly releases had the opposite problem: small fixes waited weeks to reach customers.
Two weeks is long enough to finish something meaningful and short enough that nothing waits long.
How a cycle runs#
The first week is for building. The second week starts with a feature freeze on Wednesday, then testing, documentation and the changelog. Release goes out on Tuesday morning, European time, which is early enough to fix anything before the US wakes up.
Feature flags do the heavy lifting#
Bigger features take more than two weeks. They ship in pieces behind feature flags, turned on for our own workspace first, then for agencies who asked for early access, then for everyone. Frame-accurate video review took three cycles that way.
The changelog is part of the release#
A change isn't shipped until it's in the changelog, written in plain language, saying what changed and why. Writing it is part of the work, not an afterthought. It's also a good test: if we can't explain a change in a few sentences, it's probably not ready.
The rhythm also helps customers plan. Agencies know when changes arrive, so a new feature never surprises them in the middle of a client review.
You can follow every release on our changelog, or subscribe to it by RSS.
