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

Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>

pep-0596.rst

@@ -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:

pep-0602.rst

@@ -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:
@@ -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
@@ -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

pep-0619.rst

@@ -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:

pep-0664.rst

@@ -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:

pep-0693.rst

@@ -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: