-
What versioning scheme would make sense for this package?
I'm debating between the following two options:
- [SemVer](https://semver.org/): `MAJOR.MINOR.PATCH`
- [CalVer](https://calver.org/): `…
-
As explained in the [Docker development best practices](https://docs.docker.com/develop/dev-best-practices/) documentation:
> Do not rely on the automatically-created latest tag.
We need to crea…
-
There's already a thread #200 discussing the necessity of extending the three-number SemVer notation to indicate tiniest nightly changes. In this thread i would like to discuss the necessity of the op…
-
Thanks for maintaining this awesome list. I'd like to suggest to add a release when a change is made to the README file. With this, we can watch the project without getting lots of activity emails.
-
(Expanding on #149)
Now there is one tagged release (v2.4.1). But is there a policy and mechanism for future releases?
It would be great to have a plan for when to increment the version number a…
-
Two weeks gap is approximate time for this package to reach conda and other package managers after pip release.
This gap will decrease the time when a user sees this error message but can't get rid o…
-
* Switch to normal semver versioning
* Create release tags on github
* Release packages on PyPi
This allows people to use this package in a standard pythonic way which is a big advantage for thos…
jobec updated
5 years ago
-
As per https://github.com/pypa/pip/issues/4981#issuecomment-382853909, here's a dedicated issue for discussing the next major release.
As far as I can tell, we have enough changes and fixes to just…
-
We had a small discussion about that after the installer release. The version number didn't increase for a long time and so we were releasing the installer under a four years old release number. I thi…
-
I'd like to discuss our version schema and the way we move forward with breaking changes. In it's current state we have a stable release but we frequently want to introduce minor interface breaking ch…