Source: https://wiki.blender.org/wiki/User:JesterKing/BlenderLtsReleaseProcessProposal
* [] LTS engineer (LTSE) lands fixes in release branch
* [] LTSE or Release team (REL) rolls release cycles (beta -> release)
* [] LTSE or REL tags (note, all involved submodules as well)
```
<on all git repros do>
git tag -a v2.83.2 -m "Tagging Blender 2.83.2 release"
git push origin v2.83.2
<enddo>
svn mkdir https://svn.blender.org/svnroot/bf-blender/tags/blender-2.83.2-release
svn copy https://svn.blender.org/svnroot/bf-blender/tags/blender-2.83.1-release https://svn.blender.org/svnroot/bf-blender/tags/blender-2.83.2-release
```
* [] REL/LTSE activates buildbot workerks
* [] REL+LTSE verify builds are ok (install, execute, no obvious misbehavior)
* [] LTSE Upload builds to download.blender.org
* [] REL Prepare packages for snapcraft.io, Steam, Windows
* [] REL Upload to snapcraft.io, Steam, windows Store
* [] REL Update maintenance release changelog on blender.org
* [] REL Update blender.org links for maintenance release
* [] LTSE or REL rolls version and cycle (i.e. 2.83.2 -> 2.83.3, and release -> beta)