-
Notifications
You must be signed in to change notification settings - Fork 21.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARO support lifecycle document modification required #121477
Comments
@QQHollyGit |
@QQHollyGit |
@AjayBathini-MSFT Also for version 4.13 and 4.14 we can see full support period is approx 11 months and 12 months, not 14 months. Can we delete the 14 months statement to avoid confusion or some explanation can be added to say how this 14 months is being calculated. |
Hello, let me jump into this. There seems to be a mistake in the table. |
The date being incorrect is fixed in #122465 We are working on updating the docs and table to be more clear about the dates. There will be a minimum of 14 months from the time the version is available as an upgrade. Which is some time before it is available as an installable version. |
Do you have any updates? |
Sorry for the delay on this. We hope to have this published next week. |
This issue was addressed, closing for now. Please let us know if this update wasn't what you were looking for. #please-close |
[0]https://learn.microsoft.com/en-us/azure/openshift/support-lifecycle#azure-red-hat-openshift-release-calendar
[1]https://access.redhat.com/support/policy/updates/openshift
Starting with ARO version 4.12, the support lifecycle for new versions will be set to 14 months from the day of general availability.
Request:
This is causing confusion in customers and they complained below:
This document is so confusing for customer .
if [July 17 2024] is correct ,could you please request concerned team to change [14 months]description
if [October 19, 2024 ]is correct , could please update the date in the public document.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: