-
-
Notifications
You must be signed in to change notification settings - Fork 751
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
[ubuntu] Changes for new policy #5078
base: marcwrobel-patch-5
Are you sure you want to change the base?
Conversation
Co-authored-by: Marc Wrobel <[email protected]>
For the image, I think allowlisting |
eol: 2019-04-02 | ||
eoes: 2024-04-02 | ||
legacySupport: 2026-04-02 |
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.
Why not just set eoes
to 2026-04-02
and remove the legacySupport
custom column ? From what I understood the legacySupport
column will never be used again, so it seems strange to add a column for a single release.
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.
- It is unclear if Legacy Support is included as part of Ubuntu Pro, or is merely available to Ubuntu Pro subscribers (with perhaps an additional subscription)
- I'm guessing 16.04 will get Legacy Support as well, but that's 2 years away.
I'll revert the custom column changes for now, but I'm unsure about setting eoes to 2026, because of the lack of clarity.
@captn3m0, any news on this PR ? |
The new website and wiki do not use the "Hardware Maintenance" wording, so drop
eoas
column entirely. Adds a custom legacySupport column for now. And changes the ESM wording from Extended to Expanded.