[zapzupnz]

Is it really a 'dilemma' though? Basically, a project can set the version numbers how they want. They don't need to justify the change. So long as they and others can refer to each release by a simple and easily identifiable number or moniker, it really makes no difference if it's 5.0 or 4.22. In the end, the Linux kernel is such a big project that there's really no reason to single out any single or a set of changes as significant enough to warrant a version number bump; it's all arbitrary to start with.

[sys_64738]

Versioning isn't just about the practical software build. The version is used to describe differences to non-tech PMs.

A PM's eyes will glaze over when you talk 4.22 V 4.16, but you mention v22 versus v22 and then they 'get it'.

That's why a Chrome style versioning has value.

[zapzupnz]

It has value to certain people, sure. But given that it's mainly technically minded people who work with the kernel on a daily basis, and most people don't need to know their kernel version number outside of limited circumstances.

I would say for the majority of Linux users, it's the OS version that's more important; that is, getting help with your installation of Ubuntu, it's more useful to know that you're running 18.10 rather than kernel version 4.18.

Yes, Chrome-style versioning has value. But is that value applicable to this scenario? I wouldn't say 'no', but I'm fairly comfortable saying "not necessarily". Nothing is universal, and no one solution solves every problem.