Right, the fifth beta of 1.27.0 just released:
Why wait for 1.27.1 and not just include a fix for testing in the current 1.27.0 beta releases? I would love to know what was the decision process for this bug, especially knowing how disruptive it is for some people.
