[Bf-committers] Committing fixes for releases in stabilizing branch.
Brecht Van Lommel
brechtvanlommel at gmail.com
Fri Oct 11 21:53:33 CEST 2019
* Announcement email sent
* source/tools now has blender-v2.81-release
* Autoclose on release branch hopefully fixed, but it might not
retroactively close tasks that were fixed already.
We accidentally had a merge of master into the release branch. I reverted
that now, but we should add code on git.blender.org to prevent this.
On Fri, Oct 11, 2019 at 8:25 PM Bastien Montagne <montagne29 at wanadoo.fr>
> Also, looks like phabricator needs some tweaking, it’s not catching bug
> fixes and other phab object references from commits to the release
> branch (e.g.
> for https://developer.blender.org/T70695).
> I know phab is sometimes slow to parse commits in new/quiet branches,
> but after 1h30 I think there is something else at play here. ;)
> On 11/10/2019 18:45, Bastien Montagne wrote:
> > 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,
> > Bastien
> > 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
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers