@wycats wrote:
Yes. 1.13 is the only release so far that has included deprecations to public APIs that will be removed in the next release. The next time that will happen will be in the lead-up to 3.0.
@guarav has some reasonable critiques about the exact details of what we have done here. Keep in mind, though, that Ember 2.0 is the first time a major library on a six-week-release cycle has bumped a major version. We're still learning a lot, and definitely expect to make fewer mistakes in the 3.0 major release.
Part of our strategy has been to aggressively communicate what we're doing and our plans. While that has not eliminated the pain, it at least has made our plans clear, and has given people an opportunity to weigh in as we have progressed.
Going forward, I really recommend that people who care a lot about improving the process contribute to other ongoing proposals to improve things in the 2.x cycle like Release Cycle Improvements and Deprecation Warning Handlers. If you feel like the process isn't going well for a specific significant change (like, say, ES6 modules), please raise the alarm.