What does “final” mean? Stability that’s been validated across a wide range of use cases, and a framework that’s been optimized for developer productivity, small payload size, and performance. With ahead-of-time compilation and built-in lazy-loading, we’ve made sure that you can deploy the fastest, smallest applications across the browser, desktop, and mobile environments. This release also represents huge improvements to developer productivity with the Angular CLI and styleguide.
Angular 1 首先为新兴的 Web 技术解决了如何开发的问题。六年后的今天，开发人员面对的挑战是：应用程序必须支持多种多样、千变万化的设备。在这次发布中，我们有了更强力的路由器、表单和其它核心 API 。现在，你可以为任何平台构建酷炫的应用了。也许你会更喜欢用自己的方式工作， Angular 同样是模块化并富有弹性的，这样你就可以自由使用你喜欢的第三方库了??或是自己写一个！
Angular 1 first solved the problem of how to develop for an emerging web. Six years later, the challenges faced by today’s application developers, and the sophistication of the devices that applications must support, have both changed immensely. With this release, and its more capable versions of the Router, Forms, and other core APIs, today you can build amazing apps for any platform. If you prefer your own approach, Angular is also modular and flexible, so you can use your favorite third-party library or write your own.
From the beginning, we built Angular in collaboration with the open source development community. We are grateful to the large number of contributors who dedicated time to submitting pull requests, issues, and repro cases, who discussed and debated design decisions, and validated (and pushed back on) our RCs. We wish we could have brought every one of you in person to our meetup so you could celebrate this milestone with us tonight!
We heard loud and clear that our RC labeling was confusing. To make it easy to manage dependencies on stable Angular releases, starting today with Angular 2.0.0, we will move to semantic versioning. Angular versioning will then follow the MAJOR.MINOR.PATCH scheme as described by semver:
当对标为稳定的 API 进行不兼容的变更时，增加主版本号（ MAJOR ），
the MAJOR version gets incremented when incompatible API changes are made to stable APIs,
当添加了向后兼容的功能时，增加次版本号（ MINOR ），
the MINOR version gets incremented when backwards-compatible functionality are added,
当以向后兼容的方式修复了 bug 时，增加补丁号（ PATCH ）。
the PATCH version gets incremented when backwards-compatible bug are fixed.
迁移到语义化版本方案可以确保我们的组件和工具等生态圈能快速用到最新特性。虽然即使保持了一致而可靠的开发环境，产品级应用仍然会依赖于主版本之间的稳定性，但这对 BUG 修复和发布新 API 来说仍然是显著的优点。
Moving Angular to semantic versioning ensures rapid access to the newest features for our component and tooling ecosystem, while preserving a consistent and reliable development environment for production applications that depend on stability between major releases, but still benefit from bug fixes and new APIs.