We’re changing how and when new features become available to you. New features will still be deployed every 3 weeks, but the actual release of new features now follows a split schedule: some go live on Wednesday (as before), others go live the following Monday.
The long-term goal is to make releases more predictable, less disruptive, and easier to plan for.
What this means to you
We’re rolling this change out in steps. Here’s what that looks like:
Step 1 (Before)
- New features and bug fixes all went live on Wednesday, right after deployment (which happens every 3 weeks when we update the software behind the scenes).
Step 2 (Current)
- New features follow a split schedule:
- Some go live on Wednesday, every 3 weeks.
- Others become available the following Monday, typically the higher-impact features or those that benefit from a few extra days before going live.
- Bug fixes still go live as soon as possible on Wednesday.
Each feature's actual go-live date appears in the Release Notes.
While you may see mixed timing during this step, our goal is to reduce mid-week changes, give you more time to prepare, and ensure a smoother rollout of new functionality.
Nothing changes in staging. You’ll still get access to new features in the staging environment 3 weeks before they go live in production, so you can continue testing and planning as usual.
Step 3 (Future goal)
- All new features will go live on Mondays (every 3 weeks).
Why we’re changing this
To explain, let’s clarify a bit of terminology: Deployment and release are not the same thing.
Think of it like a restaurant:
- 🛠 Deployment = The kitchen prep 👨🍳
- This is when we finish building a feature and push it to our servers. It’s ready behind the scenes, but not visible to users yet, like the food that’s cooked but still in the kitchen.
- 🚀 Release = Serving the food 🍽️
- This is when the feature becomes available to you, like bringing a finished dish to your table.
Until now, deployment and release have happened at the same time. We’re now separating them slightly. That gives us time to:
- Run final checks after deployment.
- Catch and fix any last-minute issues before they reach you.
- Reduce surprises on your end.
This shift supports smoother rollouts, better communication, and a more predictable experience for your team.
System version is updated with deployments. For example, if deployment occurs on Wednesday the 23rd, the system is considered version v123 from that point, even if some features don’t go live until the following Monday.
What's changing at a glance
Bug fixes are not affected by this change. They will continue to go live as soon as they are deployed.
How we'll communicate feature availability
We will continue publishing our Release Notes every 3 weeks on Wednesday. You’ll start seeing labels in our Release Notes that show when each feature will go live:
- For features available on Wednesday: Available on [Date]
- For features available the following Monday: Available on [Date]
What’s next
We’re working toward:
- A consistent Monday release schedule for all new features.
- Clear timelines and updates.
We expect this interim stage of staggered release to last approximately 6 months, with full rollout of the Monday-only release model planned for Q1 2026. We’ll keep you updated as we complete the transition and move fully to the Monday release schedule.