Release 0.0.1-alpha.22 · astral-sh/ty
Release 0.0.1-alpha.22 · astral-sh/ty
github.com
Release 0.0.1-alpha.22 · astral-sh/ty
6 comments
-
-
Really don't understand why post about a dev pre-release? It's confusing, what is the goal trying to achieve with this post?
And why not using semantic versioning?
pycon
>>> from packaging.version import Version >>> v = Version("0.0.1-alpha.22") >>> str(v) '0.0.1a22' >>>0.0.1alpha22 or 0.0.1a22 although that looks alot like pre-release dev level fixes. In which case, 0.0.1a0-dev22
There is no project ever that had 22 alpha releases. That's nuts. Your alpha testers must be really overworked.
Fire the six year old in charge versioning decisions ;-)
Your welcome. Your future user base can thank me later for putting a stop to that atrocity posing as versioning
epochis used to transition from random nonsense versioning to semantic versioning.There is no shame/stigma for admitting a mistake and correcting it. Eventhough that epoch will now stick around with the project forever.
-
I posted because I was happy to see some software in growing up. If you are not comfortable, I will not post this kind again.
-
My point is to wait for an actual release, a call to action, or an article about the project. Release notes on a dev pre-release is odd.
Not discouraging you from posting. You are very welcome to post here. And btw thanks for responding.
This is the semantic versioning spec, but it'll give you nightmares.
Here are examples with explanation for each versioning component. Much easier on the eyes
gl
-
-
6 comments
Really looking forward to running type checks with pre-commit. Mypy is just too slow with most code bases.