Perhaps we should target this bug to 5.6 then? To serve as a reminder to look into this when the feature is ported to 5.6?
Perhaps we should target this bug to 5.6 then? To serve as a reminder to look into this when the feature is ported to 5.6?