As an addon developer I find Anki’s versioning a bit… unfortunate. Specifically, I have a problem with Anki not using patch versioning. A lot of users are stuck with older versions of Anki since they need addons that do not support later Anki versions. So I also want to support a few older versions…

[image] New Anki beta and versioning Beta Testing Anki has a long history of not-so-great version numbers. sweat_smile Semver is a bit of a tricky subject. From the perspective of add-ons, it’s a breaking API change, and you could argue that should make it 3.…

I did see that topic, but I don’t think it ever mentions the problem with patches. Since this is a separate issue, I made a new topic. Also I don’t see the answer of how the current system is useful. It seems that the argument is that 2.0 → 2.1 was a rather big change, what with Python version chan…

[image] oakkitten: It seems that the argument is that 2.0 → 2.1 was a rather big change, what with Python version change and Qt version change from 4 to 5, and recent changes such as Qt version change to 6 is smaller, and so doesn’t warrant minor version change? I’m not sure how this makes the c…

I see. Would love to see the change happen! :purple_heart: Oh and by the way, I personally think year.month.patch would be a rather suitable versioning scheme for Anki as well.

[image] oakkitten: year.month.patch Wouldn’t you be worse off than with the current scheme, because you decrease the amount of semantic information you can get out of the version number? year.minor.patch would at least allow to differentiate between small and big updates :thinking: Am I mis…

If 2.1.45+ corresponded to 21.7.0~21.7.4 and 2.1.50+ to 22.4.0~22.4.4, there’s more semantic info than what we currently have where only the patch number is used.

I see, but the value of the year and month info depends on the release strategy. If you align releases with the calendar (major updates with new year, minor releases with starting months and patches any time), then I’d agree that it has more meaning. Knowing the date by itself is not as useful as b…

Large updates would get a date bump, minor updates would get a patch bump. It’s effectively major+patch, with no separate minor number, with a year/month instead of an incrementing number.

would at least allow to differentiate between small and big updates The last big change was Qt5 → Qt6 I guess. As for me, this was a very minor change, supporting Qt6 even without Qt5 compatibility mode was a breeze. However the same version introduced changes in how Editor draws buttons, which m…

Use a different versioning system? SemVer, perhaps?

Anki Help

dae May 19, 2022, 3:39am 6

Agreed, that is what I am leaning towards using in the future.

Anki 2.1.66 Beta

Topic		Replies	Views
New Anki beta and versioning Beta Testing	9	1716	November 4, 2022
New toolkit and packaging test (Windows) Beta Testing	26	2314	October 25, 2021
Potentially change version naming? Suggestions	15	350	July 17, 2025
Anki update numbering Suggestions	2	307	August 15, 2021
"Check for updates" button? Suggestions	20	2924	December 6, 2024

Use a different versioning system? SemVer, perhaps?

Related topics