Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Switch to Calendar Versioning
See original GitHub issueRationale
Currently, many projects related to Python packaging are CalVer’d. Among them, there are pip, virtualenv. pipenv.
Also, there are some articles explaining why SemVer isn’t so good:
- https://bernat.tech/posts/version-numbers/
- https://hynek.me/articles/semver-will-not-save-you/
- https://snarky.ca/why-i-dont-like-semver/
Specification
PDM is also a heavy CLI app that has no guarantee of backward compatibility. Commands and options may change from time to time. So, PDM would also likely follow this pattern. We choose a three-part CalVer: <year>.<month>.<seq>, where:
yearis a two-digit number representing the year.monthis a number without leading zerosseqis a 0-indexed number representing the sequence of release in this month
Example
21.5.0 The first release of May 2021
21.5.1 The second release of May 2021.
Downsides?
The dramatic jump of version number may scare people.
When will it be changed.
The final decision isn’t made yet. It may happen at around mid-2021.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Even though it’d be longer, I’d highly recommend going with the full year as the first year to make it clear that it’s a year and not just rapid-churn semver.
The next release 1.6.0 will be around the first week of June, which is a coincidence that it fits with the calendar. 🎉