home.social

#calver — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #calver, aggregated by home.social.

  1. team not only delivers but also makes things easier. With the latest version, we changed version numbering method to for better orientation, and there are many new features as well, like CDN add-on or context for LLM-based MT engines. And many more abbreviations! Give it a read and upgrade. Welcome 2026.5 weblate.org/news/archive/numbe

  2. #Weblate team not only delivers but also makes things easier. With the latest version, we changed version numbering method to #CalVer for better orientation, and there are many new features as well, like CDN add-on or context for LLM-based MT engines. And many more abbreviations! Give it a read and upgrade. Welcome 2026.5 weblate.org/news/archive/numbe #YourSoftwareYourLanguage #OpenSource #LibreSoftware

  3. #Weblate team not only delivers but also makes things easier. With the latest version, we changed version numbering method to #CalVer for better orientation, and there are many new features as well, like CDN add-on or context for LLM-based MT engines. And many more abbreviations! Give it a read and upgrade. Welcome 2026.5 weblate.org/news/archive/numbe #YourSoftwareYourLanguage #OpenSource #LibreSoftware

  4. #Weblate team not only delivers but also makes things easier. With the latest version, we changed version numbering method to #CalVer for better orientation, and there are many new features as well, like CDN add-on or context for LLM-based MT engines. And many more abbreviations! Give it a read and upgrade. Welcome 2026.5 weblate.org/news/archive/numbe #YourSoftwareYourLanguage #OpenSource #LibreSoftware

  5. #Weblate team not only delivers but also makes things easier. With the latest version, we changed version numbering method to #CalVer for better orientation, and there are many new features as well, like CDN add-on or context for LLM-based MT engines. And many more abbreviations! Give it a read and upgrade. Welcome 2026.5 weblate.org/news/archive/numbe #YourSoftwareYourLanguage #OpenSource #LibreSoftware

  6. Black 26.1.0 is out.

    For those who don't know, they use CalVer, and a new year means a new style with some formatting changes. So far they look good to me.

    github.com/psf/black/releases/

    #Python #Black #CalVer

  7. Black 26.1.0 is out.

    For those who don't know, they use CalVer, and a new year means a new style with some formatting changes. So far they look good to me.

    github.com/psf/black/releases/

    #Python #Black #CalVer

  8. Black 26.1.0 is out.

    For those who don't know, they use CalVer, and a new year means a new style with some formatting changes. So far they look good to me.

    github.com/psf/black/releases/

    #Python #Black #CalVer

  9. Black 26.1.0 is out.

    For those who don't know, they use CalVer, and a new year means a new style with some formatting changes. So far they look good to me.

    github.com/psf/black/releases/

    #Python #Black #CalVer

  10. Black 26.1.0 is out.

    For those who don't know, they use CalVer, and a new year means a new style with some formatting changes. So far they look good to me.

    github.com/psf/black/releases/

    #Python #Black #CalVer

  11. Эволюция методологий версионирования

    Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

    habr.com/ru/articles/982740/

    #EvoVer #SemVer #CalVer #версионирование #версия

  12. Эволюция методологий версионирования

    Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

    habr.com/ru/articles/982740/

    #EvoVer #SemVer #CalVer #версионирование #версия

  13. Эволюция методологий версионирования

    Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

    habr.com/ru/articles/982740/

    #EvoVer #SemVer #CalVer #версионирование #версия

  14. Эволюция методологий версионирования

    Привет, Хабр. Всех с наступившим Новым Годом. На днях наткнулся на статью Махмуда Хашеми , в которой обсуждаются некоторые недостатки методологии семантического версионирования (SemVer) , и в качестве решения этих недостатков предлагается использовать календарное версионирование (CalVer) . В организации, где я работаю, по стандарту разработки требуется обязательно версионировать приложения по SemVer. Из собственного опыта использования SemVer скажу, что нашёл в ней ещё ряд недостатков, для исправления которых пришлось искать новый способ версионирования.

    habr.com/ru/articles/982740/

    #EvoVer #SemVer #CalVer #версионирование #версия

  15. @brettcannon

    Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where makes more sense.

    What would be a great improvement, especially for , is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

    > python -V
    Python 3.13.7 SemVer 2025-08-14

  16. @brettcannon

    Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

    What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

    > python -V
    Python 3.13.7 SemVer 2025-08-14

  17. @brettcannon

    Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

    What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

    > python -V
    Python 3.13.7 SemVer 2025-08-14

  18. @brettcannon

    Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

    What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

    > python -V
    Python 3.13.7 SemVer 2025-08-14

  19. @brettcannon

    Generally I find SemVer as the best versioning scheme. One of the few exceptions is for OS's, where #CalVer makes more sense.

    What would be a great improvement, especially for #SemVer, is if it would show better that a project is using it. Both in the repo and like here when doing "--version" in the CLI. Icing on the cake would be if release date also shows:

    > python -V
    Python 3.13.7 SemVer 2025-08-14

  20. @commanderred Wir machen doch jetzt #CalVer um endgültig die Bedeutung bei diesen Zahlen zu verlieren

  21. @commanderred Wir machen doch jetzt #CalVer um endgültig die Bedeutung bei diesen Zahlen zu verlieren

  22. @commanderred Wir machen doch jetzt #CalVer um endgültig die Bedeutung bei diesen Zahlen zu verlieren

  23. @commanderred Wir machen doch jetzt #CalVer um endgültig die Bedeutung bei diesen Zahlen zu verlieren

  24. @commanderred Wir machen doch jetzt #CalVer um endgültig die Bedeutung bei diesen Zahlen zu verlieren

  25. The obvious advantage of #CalVer is that you can immediately tell when a package was released.

    For example, it is clear that 2025.7.34 was released on 34th of July, 2025.

  26. The obvious advantage of #CalVer is that you can immediately tell when a package was released.

    For example, it is clear that 2025.7.34 was released on 34th of July, 2025.

  27. The obvious advantage of #CalVer is that you can immediately tell when a package was released.

    For example, it is clear that 2025.7.34 was released on 34th of July, 2025.

  28. The obvious advantage of #CalVer is that you can immediately tell when a package was released.

    For example, it is clear that 2025.7.34 was released on 34th of July, 2025.

  29. The obvious advantage of #CalVer is that you can immediately tell when a package was released.

    For example, it is clear that 2025.7.34 was released on 34th of July, 2025.

  30. Zaletą #CalVer jest to, że na pierwszy rzut oka można powiedzieć, kiedy wydano daną paczkę.

    Tak na przykład wiadomo, że 2025.7.34 wydano 34. lipca 2025 roku.

  31. Zaletą #CalVer jest to, że na pierwszy rzut oka można powiedzieć, kiedy wydano daną paczkę.

    Tak na przykład wiadomo, że 2025.7.34 wydano 34. lipca 2025 roku.

  32. Zaletą #CalVer jest to, że na pierwszy rzut oka można powiedzieć, kiedy wydano daną paczkę.

    Tak na przykład wiadomo, że 2025.7.34 wydano 34. lipca 2025 roku.

  33. Zaletą #CalVer jest to, że na pierwszy rzut oka można powiedzieć, kiedy wydano daną paczkę.

    Tak na przykład wiadomo, że 2025.7.34 wydano 34. lipca 2025 roku.

  34. Zaletą #CalVer jest to, że na pierwszy rzut oka można powiedzieć, kiedy wydano daną paczkę.

    Tak na przykład wiadomo, że 2025.7.34 wydano 34. lipca 2025 roku.

  35. #CalVer jest super! Zwłaszcza, jak nie przewidzisz możliwości wydania więcej niż jednej wersji tego samego dnia, więc jesteś już dwa dni do przodu!

    pypi.org/project/types-setupto

    #Gentoo #Python

  36. #CalVer jest super! Zwłaszcza, jak nie przewidzisz możliwości wydania więcej niż jednej wersji tego samego dnia, więc jesteś już dwa dni do przodu!

    pypi.org/project/types-setupto

    #Gentoo #Python

  37. #CalVer jest super! Zwłaszcza, jak nie przewidzisz możliwości wydania więcej niż jednej wersji tego samego dnia, więc jesteś już dwa dni do przodu!

    pypi.org/project/types-setupto

    #Gentoo #Python

  38. #CalVer jest super! Zwłaszcza, jak nie przewidzisz możliwości wydania więcej niż jednej wersji tego samego dnia, więc jesteś już dwa dni do przodu!

    pypi.org/project/types-setupto

    #Gentoo #Python

  39. #CalVer jest super! Zwłaszcza, jak nie przewidzisz możliwości wydania więcej niż jednej wersji tego samego dnia, więc jesteś już dwa dni do przodu!

    pypi.org/project/types-setupto

    #Gentoo #Python

  40. #CalVer is doing great! Especially when your scheme doesn't account for multiple releases in a single day, so you're now two days ahead with releases!

    pypi.org/project/types-setupto

    #Gentoo #Python

  41. #CalVer is doing great! Especially when your scheme doesn't account for multiple releases in a single day, so you're now two days ahead with releases!

    pypi.org/project/types-setupto

    #Gentoo #Python

  42. #CalVer is doing great! Especially when your scheme doesn't account for multiple releases in a single day, so you're now two days ahead with releases!

    pypi.org/project/types-setupto

    #Gentoo #Python

  43. #CalVer is doing great! Especially when your scheme doesn't account for multiple releases in a single day, so you're now two days ahead with releases!

    pypi.org/project/types-setupto

    #Gentoo #Python

  44. #CalVer is doing great! Especially when your scheme doesn't account for multiple releases in a single day, so you're now two days ahead with releases!

    pypi.org/project/types-setupto

    #Gentoo #Python

  45. 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.
    mastodon.social/@andrewnez/112

  46. 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.
    mastodon.social/@andrewnez/112

  47. 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.
    mastodon.social/@andrewnez/112

  48. 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.
    mastodon.social/@andrewnez/112

  49. 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.
    mastodon.social/@andrewnez/112

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

    github.com/python/steering-cou

    #Python #CalVer #CalendarVersioning #PEP2026