[Bf-committers] Preparing for 2.83 bcon2
Nathan 'jesterKing' Letwory
nathan at blender.org
Wed Mar 18 15:17:36 CET 2020
sorry for the confused messaging. We _are_ going to bcon2. I was just
too early with the branching messaging, which happened because I
misinterpreted the dev meeting notes.
So, bcon2 is there with exception of sequencer disk cache that
Sergey Sharybin and Richard Antalik still try to finalize.
Other than that it is bug fixing and stabilizing. The branching will
happen when we do move to bcon3 in April.
Happy improving and stabilizing!
On Wed, 18 Mar 2020 at 15:54, Nathan 'jesterKing' Letwory
<nathan at blender.org> wrote:
> I meant obviously move to bcon3...
> On Wed, 18 Mar 2020 at 15:38, Nathan 'jesterKing' Letwory
> <nathan at blender.org> wrote:
> > Hi all,
> > Just a quick heads-up that I'll be creating the blender-v2.83-release
> > branch soon and make the necessary commits and pushes to have
> > us enter bcon2 for 2.83.
> > I have pulled blender.git such that I'll be using efdc93fcc6923a735
> > from master, and I'll be using the respective masters for each
> > submodule as follows:
> > 'release/datafiles/locale' commit 885c753570b09
> > 'release/scripts/addons' commit 6665bb9820c46
> > release/scripts/addons_contrib' commit 9468c406fb5
> > 'source/tools' commit 4a6f1706258439
> > To prepare yourself for bcon2 please revisit the documentation
> > on how to work with the stabilization branch  & 
> > I'll write on this list again when I've completed the motions.
> > /Nathan
> >  https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
> >  https://wiki.blender.org/wiki/Process/Playbook_Merge_Handling
More information about the Bf-committers