Skip to content

Commit 1606cbc

Browse files
[3.12] gh-105844: Use devguide terminology to denote versions (GH-105882) (#105892)
(cherry picked from commit dba7217) Co-authored-by: Erlend E. Aasland <[email protected]>
1 parent 6baddd9 commit 1606cbc

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Doc/faq/general.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ Python versions are numbered "A.B.C" or "A.B":
135135

136136
See :pep:`6` for more information about bugfix releases.
137137

138-
Not all releases are bugfix releases. In the run-up to a new minor release, a
138+
Not all releases are bugfix releases. In the run-up to a new feature release, a
139139
series of development releases are made, denoted as alpha, beta, or release
140140
candidate. Alphas are early releases in which interfaces aren't yet finalized;
141141
it's not unexpected to see an interface change between two alpha releases.
@@ -297,9 +297,9 @@ How stable is Python?
297297

298298
Very stable. New, stable releases have been coming out roughly every 6 to 18
299299
months since 1991, and this seems likely to continue. As of version 3.9,
300-
Python will have a minor new release every 12 months (:pep:`602`).
300+
Python will have a new feature release every 12 months (:pep:`602`).
301301

302-
The developers issue "bugfix" releases of older versions, so the stability of
302+
The developers issue bugfix releases of older versions, so the stability of
303303
existing releases gradually improves. Bugfix releases, indicated by a third
304304
component of the version number (e.g. 3.5.3, 3.6.2), are managed for stability;
305305
only fixes for known problems are included in a bugfix release, and it's

0 commit comments

Comments
 (0)