Starting with WooCommerce 9.8, we are updating our release process to improve efficiency, stability, and transparency. These changes aim to make the release process more predictable for developers consuming WooCommerce, as well as those contributing to the project, in addition to making the process more manageable for our internal teams.
Key changes to the release process
Introduction of the Alpha period
Starting with WooCommerce 9.8, an Alpha period will be included in the release cycle to provide earlier access to upcoming changes.
The idea behind introducing an Alpha period is to align with WordPress Core’s approach. WordPress provides an Alpha period before tagging Betas, which allows for an early testing phase. During the Alpha period, trunk remains open for commits, and the latest nightly build will contain the most up-to-date code ahead of the Beta & Feature Freeze.
Shorter Beta + RC periods
The Beta and Release Candidate (RC) phases are being shortened while maintaining the overall 5-week release cycle:
| Version | Beta + RC Duration |
|---|---|
| Current | 5 weeks |
| 9.8 | 4 weeks |
| 9.9+ | 3 weeks |
We are ramping up to this process, and starting with WooCommerce 9.9, the final version of this new release cycle will be in place.
Timeline for upcoming releases
WooCommerce 9.8:
- Alpha period: February 24
- Beta & Feature Freeze: March 3
- RC: March 17
- Release: March 31
WooCommerce 9.9:
- Alpha period: March 31
- Beta & Feature Freeze: April 14
- RC: April 28
- Release: May 5
You can see our updated release calendar here.
What will final release timeline look like in 9.9+?
| Milestone | Timeline before release | What’s happening at this point? |
|---|---|---|
| Alpha period | T-5 weeks | Development continues, trunk open for commits |
| Feature Freeze & Beta Release | T-3 weeks | No new features; only bug fixes allowed |
| Release Candidate (RC) | T-1 week | Last round of testing; fixes in the release branch will continue to be merged to trunk |
| Final Release | Release Day (T=0) | Stable version is released |
Why these changes?
- More Agility: By reducing the feature freeze window, we ensure releases are easier to manage and smaller in scope.
- Improved Testing & Stability: In this new process, all bugs introduced in the upcoming release and found during release testing will be fixed before the release or reverted/disabled to be addressed in the next cycle, thereby reducing last-minute risks.
- Better Communication: A streamlined process makes it easier for internal and external contributors to follow along and participate in testing.
How can you get involved?
- We encourage you to test builds during the Alpha and Beta versions and provide feedback.
- Contributors should note the new feature freeze timing and plan accordingly.
- As we refine this process, we welcome feedback on the Alpha period:
- Would providing tagged Alpha versions with a downloadable zip improve clarity?
- Would simply encouraging testing of nightly builds during this phase be more effective?
We know these changes are significant, and we’re eager to hear your thoughts. Join us for Office Hours on March 26, 2025, to discuss Core Releases, or share your feedback in the comments below!
Leave a Reply