[sane-devel] Changing versioning scheme (1.1.0, 1.2.0, 1.3.0 instead of 1.0.33, 1.0.34, 1.0.35)

[Till Kamppeter]

We could keep the so-version in each generation, that is also done in 
CUPS and cups-filters. But then one could only add new features/symbols 
on an increase of the second part and not remove anything. This reduces 
the so-version bumps and the need to take care of compatibility here.

    Till

On 27/12/2021 19:27, m. allan noah wrote:
> Sounds like you are proposing something different from what Till 
> described. I think what you suggest is a fine alternative, and it does 
> not conflict with the sane standard: 
> https://sane-project.gitlab.io/standard/api.html#version-control 
> <https://sane-project.gitlab.io/standard/api.html#version-control>
> We must be careful not to break compatibility, say by accidentally 
> bumping the soversion.
> 
> allan
>