Skip to content

Commit 1935669

Browse files
jeanaswebknjaz
andauthored
Apply suggestion from @webknjaz
Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <[email protected]>
1 parent bd555c5 commit 1935669

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

source/discussions/versioning.rst

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,22 @@ number, and to decide which should be the next version number for a new release
6363
of a package. Two versioning schemes are commonly used for Python packages,
6464
semantic versioning and calendar versioning.
6565

66+
.. caution::
67+
68+
The decision which version number to choose is up to a
69+
project's maintainer. This effectively means that version
70+
bumps reflect the maintainer's view. That view may differ
71+
from the end-users' perception of what said formalized
72+
versioning scheme promises them.
73+
74+
There are known exceptions for selecting the next version
75+
number. The maintainers may consciously choose to break the
76+
assumption that the last version segment only contains
77+
backwards-compatible changes.
78+
One such case is when security vulnerability needs to be
79+
addressed. Security releases often come in patch versions
80+
but contain breaking changes inevitably.
81+
6682

6783
Semantic versioning
6884
-------------------

0 commit comments

Comments
 (0)