This fix needs to be included in a 3.1 point release, and I understand that it should backport cleanly, so I have targeted it at 3.1.7. Since it is already marked as Fix Released for the 3.2 series I am not sure whether this bug will show up when the 3.1 RM looks for fixes to include.
This fix needs to be included in a 3.1 point release, and I understand that it should backport cleanly, so I have targeted it at 3.1.7. Since it is already marked as Fix Released for the 3.2 series I am not sure whether this bug will show up when the 3.1 RM looks for fixes to include.