#Versioning

2025-06-27

喺笑公司用Java 6嘅同時,我開新VM用Ubuntu 20 only

我係咪雙重標準???

#versioning

2025-06-26

Welcome, DEVONthink 4.0 Copernicus! — Exactly twelve weeks after we published the first public beta, the beta phase is over! Here's our new DEVONthink generation with a slew of new features and improvements, from generative AI to versioning, audit-proof databases, a completely rewritten web interface, new automations and much, much more. #devonthink #devonthink4 #upgrade #update #ai #versioning #auditproof #automation #pressrelease devontechnologies.com/blog/202

2025-06-22

Last week, I had to make changes to the Helm chart for almost every service that we run. This rarely happens; usually, changes are made centrally. But this was one of those unpleasant moments. And I noticed that our developers like to use the "fix" version for releases. I saw versions like 0.1.187. I'm sure there weren't 187 bug fixes. Even a useless ML tool could fix a bug in 187 attempts xD

Anyway, I just wanted to share this link: semver.org/. Use it when you're not sure what the next version of your release should be.

#softwarereleases #softwaredevelopment #versioning #semver

2025-06-22

I'm not a big fan of automatically updating all dependencies when they don't introduce necessary features or address security vulnerabilities. But that's company policy. And when you receive information about a new release with a minor version increase, I don't expect it to take down the staging environment. For some reason, the k8s team do that a lot.

#semver #versioning

Breaking changes, v0.17.0Breaking changes, v0.16.0
2025-06-22

One topic that has been bothering me a lot lately is #versioning. And why it's so difficult for many developers. Specifically, #SemVer. It's not that hard to remember:

- Fixed a bug? Update the third number.
- Created a backward compatible feature? Update the second number.
- Need to intentionally break something? Update the first number.

It's not rocket science, after all.

And if you can't do it properly, don't use versioning in the format X.Y.Z - it just confuses everyone else.

2025-06-11

I'm not saying that semantic versioning solves all your problems, but if upgrade from 10.2.0.0 to 10.2.0.1 requires migrating databases, maybe you should consider it, it's not that bad.

#semantic #versioning #corporate #craziness #IT #DB #database

2025-06-03

At some point, you have probably worked on a text and created a duplicate to save its current state. For this purpose, DEVONthink offers document versioning. This is a backup mechanism that automatically creates versions of your document when you make edits. Here is a quick introduction to this useful feature. #devonthink #notetaking #versioning #safety #backup devontechnologies.com/blog/202

2025-04-16

New to PsyArXiv: DOI Versioning

You might have noticed some changes in how your preprints are appearing on PsyArXiv, and wondered “what the hell is going on?” The big change is that the Center for Open Science/Open Science Framework has implemented DOI (Digital Object Identifier) versioning for all of their preprint communities, including PsyArXiv. This means that every time you upload a new version of your preprint manuscript, it will be given a new DOI. It also means that URLs for papers will have a suffix like _V1 or _V2 after the unique OSF preprint identifier. You will still be able to view current and previous versions in the same way that you have previously, and the system (via Crossref) knows that each of these versions are linked. 

In practice, what does this mean for you when you’re uploading a preprint? For PsyArXiv, it won’t make much of a difference at all. You’ll still be able to upload your preprints in the same way, and upload updated versions when you need to. The only difference is that any new manuscript versions will have a different DOI to the original version.  If you are only making a change to the manuscript metadata, that won’t lead to a new DOI being minted. 

Because PsyArXiv uses a post-moderation approach, any submitted preprints will still go live immediately, and will then later go through a moderation process by our moderation team. 

DOI versioning may have an impact on your current use if you need to withdraw a preprint from PsyArXiv. For example, you might find yourself submitting to a journal that does not permit preprinting (*I guess these still exist somewhere?). When you submit a withdrawal request, it will relate to a specific version. So, if you need to ensure that all versions of a preprint are removed, you’ll need to communicate this request to PsyArXiv (e.g., submitting a withdrawal request for each version) or COS support. 

If DOI versioning isn’t going to make things different for users, you might wonder why you’d want to have different DOIs for different versions of a preprint. Well, having DOI versioning has been recommended by Crossref’s Preprint Metadata Advisory Group (see here:, Section 5.2.2 in particular), and is seen as best practice that supports an open peer review model to track review feedback and changes to the paper over time. For example, you could have an overlay journal that could use DOI versioning to track original submissions, an updated version in response to reviewer comments, and a final version accepted for publication. Another advantage is that translations of articles can have their own DOI, and different translated versions can be linked using appropriate meta-data. So, all in all, DOI versioning allows for more flexibility and opens up new possibilities for communities in terms of open reviewing. 

If you’d like a little more detail on creating a new article version, take a look at the OSF’s help guide here, and here for some more information on how DOI versioning relates to new approaches to peer review. 

I hope the above information is useful – Happy preprinting!

Dermot Lynott is an Associate Professor at Maynooth University, and the current chair of the PsyArXiv Scientific Advisory Board.

#DOI #openAccess #openResearch #openScience #preprints #versioning

2025-04-12

Understanding Semantic Versioning


Git tag v1.0.0 (MAJOR.MINOR.PATCH)

MAJOR — Breaking changes
💥
MINOR — New features

PATCH — Bug fixes
🔧

There are types of pre-release versions:

alpha — raw version of the build
beta — testing version of the build
rc — release candidate or nearly finished release

1.0.0-alpha < 1.0.0-beta < 1.0.0-rc < 1.0.0

#tech #versioning #git

Fundor333fundor333
2025-04-10

The true behind the software versioning

2025-03-28

Автоматизация версионирования в Kotlin Multiplatform: Решение для Android и iOS

Привет, Хабр! В этой статье я делюсь решением, как настроить версионирование приложения для Android и iOS с помощью Kotlin Multiplatform. Я рассказываю о том, как минимизировать человеческий фактор, автоматизировав процесс обновления версий, и как избежать дублирования информации в разных частях проекта. В статье представлен пример кода, который можно адаптировать под свой проект.

habr.com/ru/articles/895362/

#kmp #multiplatform #versioning #android #ios #compose_multiplatform #kotlin_multiplatform #kmm #mobile #kotlin

N-gated Hacker Newsngate
2025-03-27

Blender's new "Oscar-winning" version is here to finally help software enthusiasts achieve... well, nothing much really. 🤔 After all, who needs actual awards when you can navigate an endless maze of version numbers and download links instead? 🎉✨
blender.org/download/releases/

2025-03-11

#ayuda fediverso
que solucion es mejor para hacer #backup de un servidor (los archivos)?
aplicaciones en #docker , como #bludit , #forgejo , #peertube entre otras..
querria algo que tenga #versioning y soporte #s3 e idealmente interfaz web para gestionar.
estoy probando #backrest pero no veo que tenga versioning?

@t3rr0rz0n3 @matiargs @pijusmagnificus @samcre

se agradece #boost

2025-03-10

Fallthrough episode 10 is live! APIs, versioning, and HTTP. Alternatively, why semantic versioning is a lie and people don't make use of HTTP's powerful features.

fallthrough.fm/ep/10

#podcasts #software #http #api #versioning

there are two types programming language communities, identified by how they engage with semver

1. the type that labels a package version 0.32474 after its been used in mission critical production code making billions of dollars and literally saving Earth from the goa’uld because, like, the API just isn't stable yet

2. the type that are on version 312.2.42 after a full month of being out. 311 has an optional config change. 313 is going to seem like it does nothing but actually subtly inverts the behaviour of the entire API in a way that seems totally logical to the maintainers and exactly no-one else

#programming #versioning #semver

Kesharakeshara
2025-03-05

My manager flicked this one through. Just so accurate 😭

2025-03-05
Had my manager send me this is one. Just so accurate 😭

#developer #versioning

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst