docs(misc): add version-support-status page #16460
Conversation
|
This is the docs homepage showing the link to the detail page.
|
|
This is the detail page.
|
There was a problem hiding this comment.
Looking good, just some smaller change requests.
There is a section about the versioning in the FAQ. https://docs.angularjs.org/misc/faq#what-is-the-angularjs-versioning-strategy-
Can you add a link from there to the new page?
README.md
Outdated
| @@ -12,6 +12,12 @@ It also helps with server-side communication, taming async callbacks with promis | |||
| and it makes client-side navigation and deep linking with hashbang urls or HTML5 pushState a | |||
| piece of cake. Best of all? It makes development fun! | |||
|
|
|||
| ##### AngularJS will be moving to Long Term Support (LTS) mode on July 1st: [Find out more](misc/version-support-status) | |||
README.md
Outdated
|
|
||
| ##### Looking for the new Angular? Go here: https://github.com/angular/angular | ||
|
|
||
| -------------------- |
There was a problem hiding this comment.
Can you put another rule above AngularJS will be moving ... ? That'll frame it nicely
|
|
||
| ### Until July 1st 2018 | ||
|
|
||
| Any version branch not shown (e.g. 1.5.x) is no longer being developed. |
There was a problem hiding this comment.
ultra explicit: "not shown in this table"
|
|
||
| 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.
| <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> |
There was a problem hiding this comment.
To "to contain breaking changes" maybe add "and significant features"?
There was a problem hiding this comment.
I am not sure if that adds much - "significant features" is pretty vague, and the statement as it stands does not preclude such things.
| </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>1.7.0 will be the last release of AngularJS to contain breaking changes</td></tr> |
There was a problem hiding this comment.
Is this copy and paste? I think the description should stress that 1.7.x will only receive maintenance. Or just refer to the section below.
There was a problem hiding this comment.
copy + paste :-)
9b61549 to
0cda1d4
Compare
|
@Narretz PTAL |
Closes #16058
Closes #16458