On Mon, 2019-10-14 at 11:37 +0300, Nathan 'jesterKing' Letwory wrote: > On Mon, 14 Oct 2019 at 11:24, Campbell Barton <[email protected]> > 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 [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
