PEP 11: Clarify Windows support phases #2801
Conversation
This isn't a semantic change, but I just got "extended support" and "extended security updates" confused and Steve Dower had to correct me. So make it even more obvious in the text that we mean "extended support", and not "extended security updates".
| @@ -158,13 +158,15 @@ Microsoft has established a policy called product support lifecycle | |||
| [1]_. Each product's lifecycle has a mainstream support phase, where | |||
| the product is generally commercially available, and an extended | |||
| support phase, where paid support is still available, and certain bug | |||
| fixes are released (in particular security fixes). | |||
| fixes are released. Sometimes this is then followed by a third phase | |||
| called "ESU", for "extended security updates". | |||
There was a problem hiding this comment.
Perhaps mention ESU is a program of last resort? And link to https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates
| fixes are released. Sometimes this is then followed by a third phase | ||
| called "ESU", for "extended security updates". |
There was a problem hiding this comment.
I would (and did, in python/cpython#76773 (comment) ) describe ESU not as a "phase" but rather a specialized, paid program for high-volume enterprise customers, and be more explicit here (as well as below) in mentioning ESU specifically in the context of making clear the distinction with the Extended Support phase and CPython support, rather than making it part of "this lifecycle" that CPython is stated to follow below.
So, how about (incorporating @hugovk 's comments as well):
| fixes are released. Sometimes this is then followed by a third phase | |
| called "ESU", for "extended security updates". | |
| fixes are released. This is distinct from `ESU (Extended Security Updates) | |
| <https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates>`_, | |
| a specialized, paid program available to high-volume enterprise customers | |
| as a "last resort" option after the end of extended support. |
| phase is not yet expired. (We don't consider the ESU phase for this | ||
| purpose; only the "extended support" phase.) Subsequent bug fix releases | ||
| will support the same Windows releases as the original feature release | ||
| (even if the extended support phase has ended). |
There was a problem hiding this comment.
| phase is not yet expired. (We don't consider the ESU phase for this | |
| purpose; only the "extended support" phase.) Subsequent bug fix releases | |
| will support the same Windows releases as the original feature release | |
| (even if the extended support phase has ended). | |
| phase is not yet expired. (ESU is not considered supported.) | |
| Subsequent bug fix releases will support the same Windows releases | |
| as the original feature release (even if the extended support phase has ended). |
Following the above, clarifying that ESU is a specialized program, not a phase, and avoiding repeating ourselves about "extended support" too many times.
|
tbh I can't get too worked up over the precise meaning of "phase" or how we describe Microsoft's program for them, as long as the text makes it clear that for our purposes "extended support" = supported, "ESU" = not supported, and no-one has raised any concerns about that. So I'm just going to merge on the theory that it's at least better than what we have now, and then if y'all want to keep wordsmithing feel free :-). |
|
Accordingly, I went ahead and opened PR #2802 to apply those fixes and improvements, and also took the opportunity to update and clarify the language and links describing Microsoft's lifecycle policies to reflect that Windows >=10 follows a different lifecycle from that previous described there (while deferring any substantive changes to CPython's own policy to a future discussion and decision). |
* PEP 11: Elide long-obselete emacs declaration & header fields * PEP 11: Convert last footnote to inline link, fix redirect & use HTTPS * PEP 11: Apply ESU textual fixes/improvements suggested on #2801 * PEP 11: Update Windows section to clarify Fixed vs. Modern lifecycle * PEP 11: Apply reviewer-suggested tweaks Co-authored-by: Steve Dower <[email protected]>
This isn't a semantic change, but I just got "extended support" and "extended security updates" confused and Steve Dower had to correct me. So make it even more obvious in the text that we mean "extended support", and not "extended security updates".