Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

Following PEP 440 for versioning #67

Closed
vxgmichel opened this issue Sep 28, 2016 · 1 comment
Closed

Following PEP 440 for versioning #67

vxgmichel opened this issue Sep 28, 2016 · 1 comment
Labels

Comments

@vxgmichel
Copy link
Contributor

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?

@jairomoldes
Copy link
Contributor

Sounds good.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants