Process/Release Checklist

Release Checklist

This is a checklist to go over when making releases, to ensure everything has been updated.

Start New Release Cycle

When the release transitions to the stabilizing branch at the start of bcon3.


I - Before Branching

  • Check with Sergey Sharybin that pushing of new branches is possible
  • Do an actual subversion bump if needed to have everything properly organized in our doversion code.
    • I.E. block with /* Versioning code until next subversion bump goes here. */ comment should be empty.
    • Both blo_do_versions_xxx and do_versions_after_linking_xxx have to be checked.

II - Branching

  • Create blender-v3.XX-release branches for the following repositories:
    • Blender (rB)
    • Addons (rBA, /release/scripts/addons)
    • Addons Contrib (rBA, /release/scripts/addons_contrib)
    • Translations (rBT, /release/datafiles/locale)
    • Blender Dev Tools (rBDT, /source/tools)
git checkout -b blender-v3.XX-release
git push origin blender-v3.XX-release
  • Create blender-3.XX-release tag for Libraries (rBL)
svn mkdir
svn copy
  • Create blender-3.XX-release branch for the Manual (rBM)
svn mkdir
svn copy

III - After Branching

  • In the trunk branch of the Manual, update the blender_version number in manual/
  • In the master branch:
    • PROJECT_NUMBER in doc/doxygen/Doxyfile
    • BLENDER_VERSION, BLENDER_FILE_SUBVERSION in source/blender/blenkernel/BKE_blender_version.h
  • In the release branch:
    • Set BLENDER_VERSION_CYCLE to beta.
    • Update build_files/config/pipeline_config.yaml to point to the correct submodule and library branches.
    • Update and uncomment BLENDER_VERSION in build_files/build_environment/cmake/download.cmake.
  • Commit Splash screen to the release branch
    • Don't push this change before talking to the PR team - we announce to the world in social media at the same we commit the splash to the source code.
  • Merge the release branch into master, ensuring BKE_blender_version and the splashscreen remains correct.


  • Add tracks for new release branch in cmd/buildbot/conf/ and cmd/build/functions/build-branches.ps1.
  • Remove folders for unused tracks on all buildbot machines, as there may not be enough disk space for the new track otherwise.
  • Push git repo to workers and masters, and reconfigure masters.
  • Force build daily-coordinator, doc-api-coordinator and doc-manual-coordinator for both vdev and the new release track.
  • Verify that builds succeeded and are available for download.


  • Create empty release notes for next release on and
  • Update dashboard on
  • Update bcon in topic
  • Add a new release notes redirect (e.g., ->
  • Add a new Blender version milestone on Phabricator for the second next release.


Preparation for the final release:


  • Make a dedicated channel on to handle release communication
  • At least one hour before going to BCon5, send message to bf-committers and check with available core developers online that everything looks good for release.
    • Do not do that outside of reasonable work hours CET (10:00-17:00), nor during lunch break (13:00-14:00).
    • Ensure i18n (rBT, /release/datafiles/locale) is updated. Notify Bastien Montagne/mont29 so he can update the files prior to final release commits
  • Move Blender to bcon5 status:
  • Send message to bf-committers to notify about impending release commits
  • Create a Potential candidates for corrective releases task tagged with the released version. (For LTS releases, create a Blender LTS: Maintenance Task X.X instead)


  • Update release list in release/freedesktop/org.blender.Blender.appdata.xml
  • Make sure the libraries versions are updated in release/license/THIRD-PARTY-LICENSES.txt
  • Do an actual subversion bump if needed to have everything properly organized in our doversion code.
    • I.E. block with /* Versioning code until next subversion bump goes here. */ comment should be empty.
    • Both blo_do_versions_xxx and do_versions_after_linking_xxx have to be checked.
  • Version bump (in release branch)
    • BLENDER_VERSION_CYCLE in BKE_blender_version.h
  • Tag repositories (only after the build is approved):
    • blender (rB)
    • addons (rBA, /release/scripts/addons)
    • addons_contrib (rBAC, /release/scripts/addons_contrib)
    • i18n (rBT, /release/datafiles/locale)
    • tools (rBDT /source/tools)

ToDo: Tag submodules first and update hashes

git tag -a v3.3.0 -m "Tagging Blender 3.3.0 release"
git push origin v3.3.0
    • The following are not tagged: i18n SVN (rBTS), libraries (rBL)
    • The libraries (rBL) were tagged already at the start of the release cycle and do not need to be tagged again.

Release Builds

Check times when mirrors are updated. Aim to deploy files at 11:30 CET since syncing can take a while.
  • On the buildbot:
    • Trigger a vXXX-code-daily-coordinator build with package delivery.
    • Once finished, trigger vXXX-code-store-coordinator to upload builds to the stores and generate msix package
  • Manually tests builds.
  • Once ready to release, trigger vXXX-code-artifacts-deploy-coordinator to deploy the packages to and mirrors.
  • Lock uploaded files on (schg). Ask Dan McGrath to do this, can't be done from inside jail.


  • Snap
    • Final builds should be uploaded at this point, but not yet released as stable
    • Close beta and edge for this release.
    • Close candidate for previous release, if not an LTS.
    • Promote candidate channel to stable for this release.
    • Update latest/stable to match this release.
  • Steam
    • Final builds should be uploaded at this point, but not yet released in the stable branches
    • Create vX.X branch for this release and point it to the right build.
    • Point the default branch to the same build as vX.X.
    • If releasing an LTS, create a daily-X.X and devtest-X.X branch for the buildbot to push to automatically.
    • Do release announcement and any other store page changes.
  • Windows Store
    • Download msix package from and release it in the windows store.
    • Update store listings (export CSV, edit, import CSV again) with the PR release text


  • Release Notes
    • Adapt from Wiki, add artwork
  • Write press release
  • Add Splash .blend file to demo-files page
  • Update Redirection from /download/releases/{version}/ to{version}
  • Download page
    • Paths & Platforms tab
      • Update the Builds Folder and File Path for every build in every platform
      • E.g. blender-3.1.2-windows-x64.msiblender-3.2-windows-x64.msi
    • Splash & Release Notes tab
      • Update Release Features Summary, this text goes under the download section.
      • Update Splash Artwork, this shows up next to the Release Features Summary, doesn’t necessarily need to be the splash artwork, can be a cool screenshot too.
    • Announcement tab
      • This is a piece of HTML that can be displayed under the main download button. It could be used for adding a quick link to LTS versions.
  • Credits: Update page using source/tools/utils/
  • Frontpage: Add news item
  • Release Notes: Add item to list of releases
  • Thanks page: Update artwork
  • Site-wide settings (this needs certain permissions only Pablo, Francesco, Dan have)
    • Set Blender Version and Release Date in Site-wide settings
    • Check mirrors have a copy of the file, otherwise disable those without. (find the URLs below)

LTS release

In the case of an LTS release, add a new row in Download → Long-term Support → Blender X.X LTS and fill with release notes from generate-code-patch-notes buildbot build step (can be run manually too, see


  • Buildbot:
    • Update cmd/build/functions/build-branches.ps1 for stable doc version and manual version labels (for version switching menu).
    • Push git repo to workers.
  • Trigger vdev-doc-api-coordinator and vdev-doc-manual-coordinator on buildbot to update docs, afterwards check the links and version switch menu are correct.
    • Python API current is the new release
    • Manual latest is the new release
  • Check manual links are valid in Blender (see

Post Release


  • Create new BF Blender milestone for next release, with initial dates for bcon stages.


  • Snap: request tracks for the next release to be created on snapcraft forum (with BlenderRelease account), so that we will have it by the time the next cycle starts


  • Once the release is out for a while and no bugfix release is planned, update buildbot configuration to remove the track corresponding to the release.
  • In case of an LTS release, keep the track around and remove an old LTS track if needed.


  • Sync and tag Cycles "stand-alone" repository (rC)


LTS end-of-life

  • Update the LTS's page announcing the end-of-life, recommend to switch to the latest LTS. See 2.83 as reference.
  • Move the EOL release to "Previous LTS Releases" on


This is the complete list of mirrors, from which not all may be enabled for use at the moment. See the External Mirrors page in to find out which mirrors are currently enabled and ready to be used.