This issue is not a bug, and it can be fixed anytime. I will keep it open, but I don't think this needs to be fixed as part of the 3.0.0 release.