On Tue, Jun 20, 2017 at 11:15 AM, Jacob Champion <champio...@gmail.com> wrote: > On 06/20/2017 09:14 AM, William A Rowe Jr wrote: >> >> Would encourage us to wait at least a couple more days for >> other, unrelated regression reports to filter in while fixing this >> defect. But there is nothing stopping a 2.4.27 in rapid >> succession, we simply don't retroactively "retract" releases. > > > Right, re-issuing 2.4.26 isn't what I meant. I just want to patch this up as > quickly as possible so people don't standardize on the new behavior.
It's released into the wild, what is done is done.
