Comment 20 for bug 1860083

The commit landed in the 2.7 branch so the change of milestone to 2.8-beta1 seems like a mistake.

The fix won't make 2.7.4 as that's already gone to Solutions QA for testing and is due to be released tomorrow. It would take another day to retool things after that and by then we're entering the timeframe of the weekend and that would delay 2.7.4 till next week.

But it will be in 2.7.5. It will hit the 2.7.5 edge snap as soon as 2.7.4 goes out (hopefully within a day). Would that be sufficient to unblock things pending a formal 2.7.5 release?