This repository was archived by the owner on Apr 12, 2024. It is now read-only.
docs(misc): add version-support-status page #16460
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| @ngdoc overview | ||
| @name Version Support Status | ||
| @description | ||
|
|
||
| # Version Support Status | ||
|
|
||
| This page describes the support status of the significant versions of AngularJS. | ||
|
|
||
| <div class="alert alert-info"> | ||
| AngularJS is planning one more significant release, version 1.7, and on July 1, 2018 it will enter a 3 year Long Term Support period. | ||
| </div> | ||
|
|
||
| ### Until July 1st 2018 | ||
|
|
||
| Any version branch not shown in the following table (e.g. 1.5.x) is no longer being developed. | ||
|
|
||
| <table class="dev-status table table-bordered"> | ||
| <thead> | ||
| <tr><th>Version</th><th>Status</th><th>Comments</th></tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr class="security"><td><span>1.2.x</span></td><td>Security patches only</td><td>Last version to provide IE 8 support</td></tr> | ||
| <tr class="stable"><td><span>1.6.x</span></td><td>Patch Releases</td><td>Minor features, bug fixes, security patches - no breaking changes</td></tr> | ||
| <tr class="current"><td><span>1.7.x</span></td><td>Active Development</td><td>1.7.0 (not yet released) will be the last release of AngularJS to contain breaking changes</td></tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| ### After July 1st 2018 | ||
|
|
||
| Any version branch not shown in the following table (e.g. 1.6.x) is no longer being developed. | ||
|
|
||
| <table class="dev-status table table-bordered"> | ||
| <thead> | ||
| <tr><th>Version</th><th>Status</th><th>Comments</th></tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr class="security"><td><span>1.2.x</span></td><td>Long Term Support</td><td>Last version to provide IE 8 support</td></tr> | ||
| <tr class="stable"><td><span>1.7.x</span></td><td>Long Term Support</td><td>See [Long Term Support](#long-term-support) section below.</td></tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| ### Long Term Support | ||
|
|
||
| On July 1st 2018, we will enter a Long Term Support period for AngularJS. | ||
|
|
||
| At this time we will focus exclusively on providing fixes to bugs that satisfy at least one of the following criteria: | ||
|
There was a problem hiding this comment. Technically, also anything that is "easy" to add, e.g. small features, bug fixes, docs, iirc? Maybe just strip "exclusively", and then "focus" still leaves a lot of room for interpretation :) There was a problem hiding this comment. I don't think so. Once we hit LTS we really do not intend to add anything other than stuff in this list. |
||
|
|
||
| * A security flaw is detected in the 1.7.x branch of the framework | ||
| * One of the major browsers releases a version that will cause current production applications using AngularJS 1.7.x to stop working | ||
| * The jQuery library releases a version that will cause current production applications using AngularJS 1.7.x to stop working. | ||
|
|
||
| ### Blog Post | ||
|
|
||
| You can read more about these plans in our [blog post announcement](https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c). | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To "to contain breaking changes" maybe add "and significant features"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if that adds much - "significant features" is pretty vague, and the statement as it stands does not preclude such things.