But the trick here is that at least one or more releases will contain both features. This is different than saying "feature X will be replaced at the next major release. We'll tell you what to use in its place in the release announcement for the next major release."
Anyone following the betas would have seen this coming for a long time. And anyone who considers any piece of software to be mission-critical had better be following betas. There was a long cycle of release candidates when an admin could check for site issues before the release went gold. That's the whole point of having release candidates. The developers can't foresee every possible variation in how people use their product.
