#calver

Got around to adding the below blog post about #SemVer & #CalVer & all their alternatives, to my personal notes as a bookmark.

Realized that nobody has yet gone for the obvious: WhateVer, whose scheme is, you guessed it, 100% arbitrary, based on how capricious you're feeling at the time.
https://mastodon.social/@andrewnez/112673101150179676

At 20:26 Helsinki time on the 26th, I submitted PEP 2026 (calendar versioning for Python) to the steering council for consideration!

https://github.com/python/steering-council/issues/255

#Python #CalVer #CalendarVersioning #PEP2026

Here's a thorough write-up of what's new in pip 24.2 by new core team member, Richard Si:

https://ichard26.github.io/blog/2024/08/whats-new-in-pip-24.2/

And did you know pip uses calendar versioning? That 24 is the year.

https://calver.org/#other-notable-projects

#python #pip #CalVer

At 20:26 this evening I published PEP 2026 to propose Python adopts calendar versioning!

https://peps.python.org/pep-2026/

This means that starting with the 2026 release, the version will be 3.YY.micro; Python 3.15 will cease to be, and will instead be Python 3.26.

Discuss:

https://discuss.python.org/t/pep-2026-calendar-versioning-for-python/55782

Read @sethmlarson's blogpost of my Language Summit talk:

https://pyfound.blogspot.com/2024/06/python-language-summit-2024-should-python-adopt-calver.html

#PEP2026 #Python #PyConUS #PyCon #CalVer #CalendarVersioning #LanguageSummit

"This is not going to be Python 4".

I am taking this as implicit approval of @hugovk's proposal to switch to #calver.

#python #pyconus

Here are my slides from the Language Summit:

Should Python adopt CalVer?
https://hugovk.github.io/python-calver/

#PyConUS #PyCon #Python #CalVer #CalendarVersioning #LanguageSummit

I just kicked off PyCon 2024 with the first talk of the Language Summit (and my first talk at PyCon!): "Should Python adopt CalVer?" It was an interesting discussion, let's see!
#PyConUS #PyCon #Python #CalVer #CalendarVersioning #LanguageSummit

Heh, I just noticed that it looks like `virtualenv` seems to use the "COVID-time" version of #calver: https://virtualenv.pypa.io/en/latest/changelog.html

Version 20 starting in 2020, still version 20 now...

@rauschma Such a #CalVer (https://calver.org/) versioning would actually be preferable though to TypeScripts current incorrect #SemVer (https://semver.org/) versioning, as it’s currently easy to mistake a minor #TypeScript release as being non-breaking where it actually can be breaking (and 5.0 was not an actual major, it was simply a 0.1 increase from 4.9…)

(Links for general references, I know you know this stuff already)

Hey @conda switched to Calendar Versioning, nice! By unanimous vote, too: https://github.com/conda-incubator/ceps/blob/main/cep-8.md

https://calver.org for details. #conda #CalVer #python

So apparently a project switched from meaningful versioning to #CalVer but did not change the rules for SOVERSIONs. Does that mean that they break ABI for the first release every year?

https://github.com/google/flatbuffers/issues/7759

List of shame with 0ver projects (long lasting 0.x version) #SemVer #CalVer http://0ver.org