Thank you for trying to untangle this web. I'm going to comment on the incident report talk page. Pine On Fri, Sep 16, 2016 at 7:57 AM, Antoine Musso <hashar+wmf(a)free.fr> wrote:

What are your plans for when you'll deploy wmf.19, branch wmf.20 and deploy wmf.20? I ask because I have a patch lined up that I wanted to merge today right after the wmf.20 branch cut, because I want it to spend the full week on beta labs before it goes to production. I can merge that patch today and have it go to beta, and have it go into wmf.20 once it gets cut, but I'd only be willing to do that if I had a guarantee that wmf.20 would not be cut before early next week. Because it's currently unknown when wmf.20 will be cut, I don't know what's safe to do. Unrelatedly, I also have a patch merged in master that fixes a regression in wmf.19. Since wmf.19 is not deployed right now, the regression doesn't affect production, but if wmf.19 is ever going to be deployed, then the fix needs to be cherry-picked into it. Do you know if wmf.19 is going to be deployed, or is it going to be skipped? Since wmf.19 is not deployed right now, should I submit a cherry-pick to it for SWAT today so that it gets unbroken in the event it ever gets deployed? I understand that you are investigating and will reevaluate after, but it would be nice to have these questions answered quickly so we have some sense of what is and isn't going to happen, and aren't blocked by this uncertainty for much longer, On Tue, Sep 20, 2016 at 12:27 PM, Tyler Cipriani <tcipriani(a)wikimedia.org> wrote: