[pep-602] Sell the annual nature harder
This commit is contained in:
parent
2d4bb3155d
commit
6e08d96fe1
|
@ -16,7 +16,8 @@ Abstract
|
|||
|
||||
This document describes a change in the release calendar for Python
|
||||
starting with Python 3.9. This change accelerates the release cadence
|
||||
such that major versions are released every twelve months.
|
||||
such that major versions are released predictably every twelve months,
|
||||
in October every year.
|
||||
|
||||
|
||||
Implementation
|
||||
|
@ -109,7 +110,9 @@ This change provides the following advantages:
|
|||
|
||||
- creates a predictable calendar for releases where the final release is
|
||||
always in October (so after the annual core sprint), and the beta
|
||||
phase starts in late May (so after PyCon US sprints);
|
||||
phase starts in late May (so after PyCon US sprints), which is
|
||||
especially important for core developers who need to plan to include
|
||||
Python involvement in their calendar;
|
||||
|
||||
- decreases the urge to rush features shortly before "Beta 1" due to
|
||||
the risk of them "slipping for 18 months";
|
||||
|
|
Loading…
Reference in New Issue