Process/Release Checklist

Release Checklist

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

Start New Release Cycle

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


  • Update release list in release/freedesktop/org.blender.Blender.appdata.xml
  • Create blender-v2.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)
git checkout -b blender-v2.XX-release
git push origin blender-v2.XX-release
  • Create blender-2.XX-release branch for Libraries (rBL)
svn mkdir
svn copy
  • In the master branch, bump the version in:
    • PROJECT_NUMBER in doc/doxygen/Doxyfile
  • In the release branch, set BLENDER_VERSION_CYCLE to beta.
  • Merge the release branch into master, ensuring BKE_blender_version remains correct.
  • Force build both branches on buildbot, and ensure they are both visible on the download page.


  • Create empty release notes for next release on and
  • Change buildbot configuration to build new release branch
  • Update dashboard on
  • Update bcon in topic


When Blender is released in bcon5.


  • Splash screen
  • Version bump (in release branch)
    • BLENDER_VERSION_CYCLE in BKE_blender_version.h
  • 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.
  • Tag repositories:
    • blender (rB)
    • addons (rBA, /release/scripts/addons)
    • i18n (rBT, /release/datafiles/locale)
    • tools (rBDT /source/tools)
    • libraries (rBL)
    • The following are not tagged: addons contrib (rBAC), i18n SVN (rBTS)
  • Sync and tag Cycles "stand-alone" repository (rC)


  • Run automated tests
  • Run manual tests

Release Builds


    • Finish release notes
  • Ensure updated screenshots at
    • Release notes: adapt from wiki and add artwork
    • Credits page: update using source/tools/utils/
    • Sitewide settings: set Blender Version and release data
    • Front page: add news item
    • Donwload page:
      • Features & Splash 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.
      • Platforms tab
        • Update the File Path for every build in every platform.
        • E.g. blender-2.79b-windows64.msi -> blender-2.80-windows64.msi
      • Mirrors tab
        • Check that all enabled mirrors have a copy of the file, otherwise disable.
        • Release Candidate tab: turn off/on
      • 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 older versions.
  • Buildbot
    • Check that builds are shown correctly for the next release cycle


  • Freeze manual at version number and update for new version
  • Freeze API docs at version number and update for new version
  • Check manual links are valid in Blender (see