AngularJS will release another important version and enter the long-term support stage. angularjs stage
Pete Bacon Darwin, an early member of the Angular team, recently published a message on the Angular blog, saying:
At present, the team is developing AngularJS 1.7.0, and 1.7 of the development cycle will continue until June 30, 2018. From January 1, July 1, AngularJS will enter the Three-Year Long-Term Support phase (LTS ).
Pete Bacon Darwin said that the Team knows that many developers are still using AngularJS, and it takes some time and effort to migrate to Angular, but they also need developers to understand the future development plans of AngularJS.
We all know that AngularJS is the exclusive name of Angular 1, and Angular 2 is later called Angular. Angular 2 is not upgraded from Angular 1. Angular 2 uses TypeScript for rewriting. Therefore, AngularJS and Angular differ greatly, even if you have used AngularJS, angular also has a certain learning curve, which can basically be considered as a brand new framework.
However, Versions later than Angular 2, such as Angular 4, 5, and 6, can be viewed as Angular 2.4, 2.5, 2.6, the official explanation is that Angular started to use the semver semantic version and made a version alignment.
AngularJS calendar
- January 1 to June 30, 2018: AngularJS 1.7.0 development stage
- July 1-20, 2018-June 30: long-term support phase of AngularJS 1.7
All currently running AngularJS applications will work normally in the future and will be officially supported for updates. AngularJS npm, bower, and CDN can also be used.
So what does it mean to enter the long-term support stage? This means that the team only focuses on fixing errors that meet at least one of the following conditions:
- Security Vulnerability Detected in 1.7.x branch of the framework
- The version released by mainstream browsers causes applications that use AngularJS 1.7.x in the production environment to stop working.
- The version released by jQuery causes applications that use AngularJS 1.7.x in the production environment to stop working.
Therefore, the development team said that patch versions released after 1.7.0, such as 1.7.1 and 1.7.2, do not contain destructive changes, mainly to fix some bugs in the framework.