You are right. We will trigger the error just before 3.0. For now, it should only be documented in the CHANGELOG for 3.0.