Operations Working Group - First Meeting

2018-07-16 Thread Gastón Kleiman
Hi all, Thank you for responding to my previous emails - I think that we have quorum for a new working group! Many of you who have expressed interest seem to be in Europe, so I tried schedule the first meeting at a time that I hope will be friendly for people in both GMT+1 and GMT-8: *Date:*

Re: Backport Policy

2018-07-16 Thread Vinod Kone
I like how you summarized it Greg and I would vote for leaving the decision to the committer too. In addition to what others mentioned, I think committer should've the responsibility because if things break in a point release (after it is released), it is the committer and contributor who are on

Re: Backport Policy

2018-07-16 Thread Jie Yu
Greg, I like your idea of adding a prescriptive "policy" when evaluating whether a bug fix should be backported, and leave the decision to committer (because they have the most context, and avoid a bottleneck in the process). - Jie On Mon, Jul 16, 2018 at 11:24 AM, Greg Mann wrote: > My

Re: Backport Policy

2018-07-16 Thread Greg Mann
My impression is that we have two opposing schools of thought here: 1. Backport as little as possible, to avoid unforeseen consequences 2. Backport as much as proves practical, to eliminate bugs in supported versions Do other people agree with this assessment? If so, how can we find

Re: Backport Policy

2018-07-16 Thread Alex Rukletsov
Back porting as little as possible is the ultimate goal for me. My reasons are closely aligned with what Andrew wrote above. If we agree on this strategy, the next question is how to enforce it. My intuition is that committers will lean towards back porting their patches in arguable cases,