iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 11: Clarify Windows support phases (#2801) 

Clarify Windows support phases

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".
This commit is contained in:
Nathaniel J. Smith 2022-09-24 10:12:29 -07:00 committed by GitHub
parent 565cc9cd94
commit a3ada0e295
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pep-0011.txt
View File

@ -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".
CPython's Windows support now follows this lifecycle. A new feature
release X.Y.0 will support all Windows releases whose extended support
phase is not yet expired. 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. (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).
Each feature release is built by a specific version of Microsoft
Visual Studio. That version should have mainstream support when the