Comment 34 for bug 1906462

Jane,

My project was an effort to get this patch installed on production for the library. And this branch, with a minor merge conflict, does merge onto 3.11. But that alone doesn't get me to where I want to go. Fooling with production to a larger degree isn't something I want to do, so I reversed. Instead, IMO we need to upgrade production to a newer version of Evergreen, and hopefully this bug fix will be included :)

Your referenced commit doesn't cherry-pick onto 3.11.1 (nor rel_3_11) without conflict.