You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
PEP 440 provides a specification for version identification.
We already comply with it, but we could take advantage of it. For instance:
After X.Y.Z is released, we could bump to X.Y.[Z+1].dev0 in develop. This way, it is easier to know in which version a commit belongs.
Anyone should be able to make a pre-release by bumping N in X.Y.ZaN (or X.Y.ZbN or X.Y.ZrcN). This makes it easier to package an intermediate version with a particular bug fix.
We could update the release module to support these syntaxes and provide the full version to setuptools.setup.
In our case, I would consider the following patterns:
Development: X.Y.Z.devN (N could be omitted here, but it's part of the normalization)
Alpha pre-release: X.Y.ZaN
Beta pre-release: X.Y.ZbN
Release candidate: X.Y.ZrcN
Final release: X.Y.Z
What do you think?
The text was updated successfully, but these errors were encountered:
PEP 440 provides a specification for version identification.
We already comply with it, but we could take advantage of it. For instance:
X.Y.Z
is released, we could bump toX.Y.[Z+1].dev0
indevelop
. This way, it is easier to know in which version a commit belongs.N
inX.Y.ZaN
(orX.Y.ZbN
orX.Y.ZrcN
). This makes it easier to package an intermediate version with a particular bug fix.setuptools.setup
.In our case, I would consider the following patterns:
X.Y.Z.devN
(N
could be omitted here, but it's part of the normalization)X.Y.ZaN
X.Y.ZbN
X.Y.ZrcN
X.Y.Z
What do you think?
The text was updated successfully, but these errors were encountered: