docs: clarify that support schedule is subject to change #40770
Closed
Conversation
This file contains 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
jelbourn
requested review from
petebacondarwin,
IgorMinar,
gkalpak,
aikithoughts and
jessicajaniuk
|
You can preview a93c810 at https://pr40770-a93c810.ngbuilds.io/. |
aikithoughts
suggested changes
Feb 9, 2021
There was a problem hiding this comment.
I think we can shorten up this disclaimer considerably. I've offered a suggestion. Some additional information:
- The text is already in an alert; using 'disclaimer' is unnecessary.
- The phrase "ensure delivery of a high-quality platform" is also not needed. Would we ever delay a release to lower its quality? :)
- Using first person plural is usually unnecessary and can be distracting.
Let me know if you have any questions!
aio/content/guide/releases.md
Outdated
Comment on lines
73
to
74
| Disclaimer: Dates are offered as general guidance and will be adjusted by us when necessary to | ||
| ensure delivery of a high-quality platform. |
There was a problem hiding this comment.
Suggested change
| Disclaimer: Dates are offered as general guidance and will be adjusted by us when necessary to | |
| ensure delivery of a high-quality platform. | |
| Dates are offered as general guidance and subject to change. |
aio/content/guide/releases.md
Outdated
Comment on lines
96
to
97
| Disclaimer: Dates are offered as general guidance and will be adjusted by us when necessary to | ||
| ensure delivery of a high-quality platform. |
There was a problem hiding this comment.
Suggested change
| Disclaimer: Dates are offered as general guidance and will be adjusted by us when necessary to | |
| ensure delivery of a high-quality platform. | |
| Dates are offered as general guidance and subject to change. |
aio/content/guide/releases.md
Outdated
|
|
||
| </div> | ||
|
|
||
| All of our major releases are typically supported for 18 months. |
There was a problem hiding this comment.
Suggested change
| All of our major releases are typically supported for 18 months. | |
| All major releases are typically supported for 18 months. |
jelbourn
force-pushed
the
support-window
branch
2 times, most recently
from
25354a4
to
bee44cb
Compare
|
You can preview bee44cb at https://pr40770-bee44cb.ngbuilds.io/. |
aikithoughts
approved these changes
Feb 10, 2021
Initially raised due to angular#39509, this change updates our "Support policy and schedule" with the same disclaimer from the "Release frequency" section above.
jelbourn
force-pushed
the
support-window
branch
from
bee44cb
to
4b2dd82
Compare
|
You can preview 4b2dd82 at https://pr40770-4b2dd82.ngbuilds.io/. |
petebacondarwin
approved these changes
Feb 11, 2021
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Initially raised due to #39509, this change updates our "Support policy and schedule" with the same disclaimer from the "Release frequency" section above.
I debated with changing the actual numbers in this section. We could change the docs to say "17 months" support and "5 months" active support to codify the fact that we decided that -1 month is acceptable, but that felt like it wasn't really representative of the goal.