I think it would be good to address this bug for 10.1 release, though I

haven't marked it as such. I will let Andrew, the release czar, to

decide on the matter.

I have marked it 10.1.0.0 for now. There is still (a little) time to get things in for 10.1, so there's a chance that it could make it in. I will be sending out mail in a little bit with status on the 10.1 release shortly.