Angular2 was officially released during the Mid-Autumn Festival!

Angular2 was officially released during the Mid-Autumn Festival!
GuideWhat does "Final Version" mean? It means that its stability has been verified by a wide range of use cases; it means that it has been optimized for productization, file size and performance; it means that with the help of pre-compilation technology and built-in delayed loading mechanism, we are confident that you can publish the fastest and smallest applications across browsers, desktops, and mobile platforms. This means that the Angular CLI and style guide prepared for developers are greatly enhanced.

Recently, at a special meeting at Google's headquarters, we released the final version of Angular 2, the successor of Angular 1's full platform.

Angular 1 first solves the issue of development for emerging Web technologies. Six years later, developers are faced with the challenge that applications must support a variety of ever-changing devices. In this release, we have more powerful routers, forms, and other core APIs. Now, you can build amazing applications for any platform. Maybe you prefer to use your own method. Angular is also modular and flexible, so that you can freely use your favorite third-party library-or write your own!

From the very beginning, we have been working with the open-source community to build Angular. We would like to express our sincere gratitude to a large number of donors! They contributed a large number of Pull requests, Issues, and reproducible use cases. They explored and debate various design decisions, and they verified and gave feedback to each of our RC programs. We sincerely hope that we can bring every one of you to our party to celebrate this great milestone with us!

What should I do next?

Angular has been available. We are excited to welcome you to become one of countless developers who use Angular to build applications. So what will Angular do next?

The following are some recent tasks for Angular developers:

1. BUG fixes and non-destructive changes to APIs marked as stable
2. Write more development guides and online examples for your use cases
3. More work on animation
4. Angular Material 2 Library
5. Let WebWorker out of the lab
6. Develop more features for Angular Universal and support more languages
7. Further increase speed and reduce volume

Semantic version

We understand that RC version labels are somewhat confusing. To make it easier for you to manage dependencies in Angular stable versions, We will migrate from Angular 2.0.0 to the semantic version specification. Future Angular versions will follow the MAJOR. MINOR. PATCH solution described by semver:

1. When an incompatible change is made to a stable API, the main version number (MAJOR) is added ),
2. This version number (MINOR) is added when backward compatible features are added ),
3. When a BUG is fixed in backward compatible mode, add a PATCH number ).

The migration to semantic version solution ensures that our components, tools, and other ecosystems can quickly access the latest features. Even if a consistent and stable development environment is maintained, product-level applications still depend on the stability between the main versions, but this is still a significant advantage for BUG fixing and new API deployment.

From: http://mp.weixin.qq.com/s? _ Biz = MzAwODY4OTk2Mg ==& mid = 2652039373 & idx = 1 & sn = 19184621a3d0f8867f2e89d779c9c016

Address: http://www.linuxprobe.com/angular-2-publish.html