Is this bug fixed in 0.48.5 too with the backport of the bug #1089406 fix? If so, should the milestone for this be updated from 0.49 > 0.48.5?
Is this bug fixed in 0.48.5 too with the backport of the bug #1089406 fix? If so, should the milestone for this be updated from 0.49 > 0.48.5?