User:Jbakker/projects/BlenderLTS/ReleaseScript

= Blender LTS Release Script =

This page is written in sequential order and was extracted from the original release process and adapted for performance as we knew we had to do this more often. When performing a release a release engineer can do all the steps as pointing out in this page.

When performing a new release I copy the source of this page to a editor and rename the previous version with the next version. (Bad excuse for introducing batches and parameters :-) ) After the release the content of the editor is copied back including modifications that have been made.

Last commit

 * Change BLENDER_VERSION_CYCLE `BKE_blender_version.h`
 * Check versioning_280.c
 * compile, commit and push

Start Builds
Start builds on the buildbot By pressing Force build on the next pages state your e-mail and put "Blender 2.83.9 Release" as reason

Now we need to wait for half an hour for the builds to complete. During that time the source archives can be created and uploaded

Create release notes
The output of these commands are used on various platform by multiple persons normally put the release notes on blender.chat in the `blender-release` room. The html and download urls are directly copied into www.blender.org cms.

Upload builds to download.blender.org
Perform the next steps after all the builds have been successfully build.

Windows Store
Make sure it you start a developer command prompt. otherwise the process will fail.

copy file to linux for uploading

https://partner.microsoft.com/en-us/dashboard/products/9PP3C07GTVRH

Steam
Normally this step is performed by Nathan Letwory. It requires a MacOS but the process as described in https://developer.blender.org/D8429

Snap
Follow snap/README.txt in the source folder

File access on download.blender.org
Ask troubled to change the flags of the release files + source files. But normally it is done automatically.

Git tagging
Tag blender/add-ons/addons_contrib i18n and tools