-
-
Notifications
You must be signed in to change notification settings - Fork 805
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
[windows] Add 10 22H2 ESU #6435
base: master
Are you sure you want to change the base?
Conversation
products/windows.md
Outdated
releaseDate: 2022-10-18 | ||
eoas: 2025-10-14 |
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.
Not sure if we should use 2025-10-14
or 2025-11-11
as releaseDate
. I went the way that 10-21h2-iot-lts
did with having the regular release date and use eoas
as it felt closer to the rest and more true to how using 22H2 will work. Also not sure if lts: true
should be set as it's behaving like a LTS but officially something else.
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.
- A little confused, since releaseDate is currently set to 2022.
- Should this be a draft PR since Windows 10 ESU isn't live yet?
Another option is to set lts
to 2025-11-11
for the last 22H2 (Enterprise, Education, and Pro) release, and use eoes
, which we use for Extended Security Updates.
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.
Fine for me as well with extended support. I just tried to keep it in sync with already existing variants for this OS (like IoT LTS).
Setting LTS for enterprise would be wrong as it also includes Pro from non-enterprise. So it doesn't match exactly any of the existing ones.
Thanks @Falco20019 for the PR. Microsoft already use the ESU concept for some of their products: I would prefer to go with the same approach and add |
@BiNZGi Adjusted as requested. I assumed you meant |
This came up during dotnet/core#9647 (comment) and is based on the following information:
According to Microsoft,
The editions that qualify for the Windows 10 ESU include Enterprise, Education, and Pro in Commercial use
which is a subset of the current(W)
+ (most probably all of)(E)
where I'm not fully sure if IoT is included or not given the special handling in IoT having a21H2 LTS
with support until 2032 without need for ESU being paid.So I kept it just as
ESU
flag with the information retrievable by Microsoft./CC @BiNZGi for review