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

[Campbell Barton]

On Wed, 2019-10-16 at 10:23 +0200, Brecht Van Lommel wrote:
> There were 2 mailing list topics about it, and it was mentioned in
> meeting
> notes 5 times. The wiki page explains it in detail, there was a
> code.blender.org blog post and developer.blender.org front page links
> to
> information about it.
> 
> I also find it worrying that some active devs were unaware of this,
> and I
> think those devs should start paying more attention to bf-committers
> emails.
> 
> https://lists.blender.org/pipermail/bf-committers/2019-August/050136.html
> https://lists.blender.org/pipermail/bf-committers/2019-August/050153.html
> https://lists.blender.org/pipermail/bf-committers/2019-August/050126.html
> https://lists.blender.org/pipermail/bf-committers/2019-August/050173.html
> https://lists.blender.org/pipermail/bf-committers/2019-August/050178.html
> https://lists.blender.org/pipermail/bf-committers/2019-September/050182.html
> https://lists.blender.org/pipermail/bf-committers/2019-October/050218.html
> https://wiki.blender.org/wiki/Process/Release_Cycle
> https://code.blender.org/2019/10/blender-release-cycle/
> https://developer.blender.org/project/view/88/


mea culpa then! 

While I do read meeting minutes, having missed the original mail on
this topic I didn't realize the implications for the stable branch.

Now I'm left wondering why Nathan said he needs to communicate better
:|

> On Wed, Oct 16, 2019 at 2:52 AM Campbell Barton <ideasman42 at gmail.com
> >
> wrote:
> 
> > On Mon, 2019-10-14 at 11:37 +0300, Nathan 'jesterKing' Letwory
> wrote:
> > > On Mon, 14 Oct 2019 at 11:24, Campbell Barton <
> ideasman42 at gmail.com>
> > > wrote:
> > > > On Mon, 2019-10-14 at 11:15 +0300, Nathan 'jesterKing' Letwory
> > > wrote:
> > > > Some fixed change behavior, were it's disputable weather we
> would
> > > want
> > > > such changes in a release - its not just a question of
> fix/broken
> > > > state.
> > >
> > > If a fix is unclear then this should be addressed indeed. That is
> > > what this work
> > > is for.
> > >
> > > > Again, there is still no justification for this change.
> > > > Who wanted this? Why?
> > >
> > > The motive here is to separate out stabilizing work from the work
> > > done
> > > on new features in master. This has been discussed since August.
> >
> > This is still fuzzy to me, it seems this didn't go via regular
> > development communication channels?
> >
> > This is turning into a meta-topic, since I don't mean to focus on
> > _this_ particular issue, it's more an example of something I think
> we
> > shuold avoid repeating,
> > I find it worrying that a significant change the the release
> process
> > which it seems multiple active devs (including admins) where
> unaware of.
> > Without a clear outcome or statement about what will happen
> differently in
> > the future.
> >
> > I'd suggest all non-trivial changes to the release process be
> submitted
> > as proposals to developer.blender.org,
> > as well as being listed in the meeting minutes, allowing some time
> for
> > feedback before they're implemented.
> >
> > > > Currently the branch fails to merge into master.
> > > > Who is responsible for tracking down & poking people to merge
> their
> > > > work?
> > >
> > > Whoever notices such a case should feel free to notify the author
> > > whose
> > > commits fail to merge, failing that poke Brecht, Dalai or me to
> > > ensure it
> > > gets handled.
> > >
> > > /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