Skip to content

Release Cycle

Release Dates and Schedule

For information on the release dates of specific Blender versions, see the milestones on project.blender.org.

Release Cycle

A new Blender version is targeted to be released every 4 months. The actual release cycle for a specific release is longer, and overlaps the previous and next release cycle.

Branches

Work is done in two branches:

  • blender-v{VERSION}-release branch: bug fixing only for the upcoming or LTS release
  • main branch: new features and improvements for the release after that

The blender-v{VERSION}-release branch will be available for 6 weeks prior to the release date. At the same time main will be open for the next release, giving 17 weeks to add new features and improve them for the next release.

Release Phases

Each Blender version has its own release phase, indicating which types of changes are allowed to be committed and what developers are focusing on.

That means for example that Blender 4.0 can be in Beta (bug fixing only) while Blender 4.1 is in Alpha (open for new features).

Phase Description Duration Details Branch Splash Shows
Alpha New features and changes 6 weeks Add bigger features, update libraries and merge branches.

Risky changes that are likely to cause bugs or additional work must be done within the first few weeks of this phase. Afterwards only smaller and less risky changes, including small features, should be made.

The first 6 weeks overlap with the Beta & Release Candidate phases of the previous release, and many developers will focus on bug fixing.

If a new feature is too unstable or incomplete, it will be reverted before the end of this phase.

Developers dedicate a steady 1-3 days/week to the bug tracker, focusing on triaging and newly introduced bugs. 		main Alpha
11 weeks
Beta Bug fixing only 5 weeks Focus on bug fixing and getting the release ready.

Development moves to the blender-v{VERSION} release branch and the splash screen gets updated. In main Alpha for the next release starts. blender-v{VERSION}-release is regularly merged into main.

The Python API remains stable during this phase, so add-ons have time to update before the release.

High severity bugs dictate how much time developers will spend in the tracker as opposed to new features for the next release. 		blender-v{VERSION}-release Beta
Release Candidate Prepare release 1 week Stable branch is frozen to prepare for the release. Only critical and carefully reviewed bug fixes allowed.

Release candidate and release builds are made.

Developers spend a short time 5 days/week with an eye in the tracker for any unexpected high severity regression. 		blender-v{VERSION}-release Release Candidate
Release Release 1-2 days Stage where the final builds are packaged for all platforms, last tweaks to the logs and promotional images, social media, video announcements.

The final switch is flicked on blender.org for the new release to show up in the Download page. 		- -
LTS Long-term release 2 years Critical fixes from main are ported over after passing quality assurance tests. For actual LTS releases only. blender-v{VERSION}-release