[Bf-committers] Committing fixes for releases in stabilizing branch.

Bastien Montagne montagne29 at wanadoo.fr
Fri Oct 11 18:45:00 CEST 2019

This has been very badly communicated so far! This mail is fine as 
"preparation", "warning" one.

But now the branch has actually be created, without **any** message 
here? Seriously? We need an official "We entered BCon3 NOW, branch 
blender-v2.81-release has been created, all bug fixes whould now go to 
that branch" type of mail!

Also, the tools sub-repo did not get its blender-v2.81-release branch, 
when it had one for 2.78, 2.79 and 2.80, any reason to break things here?

The process is already pretty confusing, if communication is not handled 
properly we are going to get some really hectic moments…

Confused cheers,

On 10/10/2019 09:34, Nathan 'jesterKing' Letwory wrote:
> Hey all,
> Soon the stabilizing branches will be created. While not much will
> change, but there are a couple of things to keep in mind.
> Any bug fix planned for the upcoming release should go to the
> corresponding branch (e.g. `blender-v2.81-release`), followed by a
> merge to `master`.
> Take your time to verify your fixes are correct and the commits look
> good (as per usual).
> More detailed guidelines can be found on the wiki at:
> https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
> There will be a message to this list once the stabilizing branches
> have been created.
> Cheers,
> /Nathan
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list