Skip to content

Release PEPs: Use 'feature release' instead of 'minor version' to avoid ambiguity #3174

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.

Sign up for GitHub

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

Merged
erlend-aasland merged 4 commits into from
Jun 18, 2023
Merged

Release PEPs: Use 'feature release' instead of 'minor version' to avoid ambiguity #3174

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a56265c
Consistently use 'minor version' for X.Y releases
erlend-aasland Jun 16, 2023
dc79252
Revert changes in PEP-605 and PEP-3147
erlend-aasland Jun 16, 2023
4d58ddb
Address CAM's review: instead, use the established term 'feature vers…
erlend-aasland Jun 17, 2023
607839d
Update pep-0602.rst
erlend-aasland Jun 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pep-0596.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Release Schedule
--------------

Note: the dates below use a 17-month development period that results
in a 12-month release cadence between major versions, as defined by
in a 12-month release cadence between feature versions, as defined by
:pep:`602`.

Actual:
Expand Down
12 changes: 6 additions & 6 deletions pep-0602.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ 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 predictably every twelve months,
such that feature versions are released predictably every twelve months,
in October every year.


Implementation
==============

Seventeen months to develop a major version
-------------------------------------------
Seventeen months to develop a feature version
---------------------------------------------

This PEP proposes that Python 3.X.0 will be developed for around
17 months:
Expand Down Expand Up @@ -65,7 +65,7 @@ Annual release cadence

Feature development of Python 3.(X+1).0 starts as soon as
Python 3.X.0 Beta 1 is released. This creates a twelve-month delta
between major Python versions.
between Python feature versions.


Example
Expand Down Expand Up @@ -288,8 +288,8 @@ More importantly, from the perspective of the user:
users. The bigger a release is feature-wise, the more potential
problems are hiding in "point zero releases".

Double the release cadence to achieve 9 months between major versions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Double the release cadence to achieve 9 months between feature versions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This was originally proposed in :pep:`596` and rejected as both too
irregular and too short. This would not give any of the benefits of
Expand Down
2 changes: 1 addition & 1 deletion pep-0619.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Release Schedule
---------------

Note: the dates below use a 17-month development period that results
in a 12-month release cadence between major versions, as defined by
in a 12-month release cadence between feature versions, as defined by
:pep:`602`.

Actual:
Expand Down
2 changes: 1 addition & 1 deletion pep-0664.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Release Schedule
---------------

Note: the dates below use a 17-month development period that results
in a 12-month release cadence between major versions, as defined by
in a 12-month release cadence between feature versions, as defined by
:pep:`602`.

Actual:
Expand Down
2 changes: 1 addition & 1 deletion pep-0693.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Release Schedule
---------------

Note: the dates below use a 17-month development period that results
in a 12-month release cadence between major versions, as defined by
in a 12-month release cadence between feature versions, as defined by
:pep:`602`.

Actual:
Expand Down