[Privoxy-devel] Changing the Privoxy version number scheme

[Fabian Keil]

I'd like to change the Privoxy version number scheme after
the 3.0.34 release.

At the moment the Privoxy version numbers look like they
might follow the semantic versioning scheme [0] but actually
we just bump the last number at each release even if
there are incompatible changes.

In the past we used even last numbers for stable releases
and uneven numbers for beta releases but we stopped releasing
beta versions as they weren't properly tested by users or
picked up by distributions.

Another problem with the current scheme is that it doesn't
work when updating binary packages. For example it might make
sense to release new Windows packages when there's a MbedTLS
vulnerability but at the moment it's not clear what kind
of version to use for such an update.

For my own projects I nowadays usually just use a date
as the version number followed by a git hash. For example
the last zogftw [1] release is 2022-06-25-03982c7.

This is easy to automate but one downside is that it's not
obvious how many releases occurred between two releases.
I'm not sure how important this is, though.

Any opinions about this?

Fabian

[0] <https://semver.org/>
[1] <https://www.fabiankeil.de/gehacktes/zogftw/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-devel/attachments/20230103/a214c8d8/attachment.bin>