Growing major version

When Michael was the lead maintainer, he followed the kernel version closely (weeks or a month).

I have been following it too, more or less, but not so closely. I wasn't happy by the fact that the project also documents glibc, but the versioning and name seems to imply that it only cares about the kernel. I think decoupling the versioning would be positive.

And after all, the version of the manual pages isn't very meaningful. We sometimes document stuff from the next kernel release, before it's even released.

The rule of thumb should be: always take the latest version of the manual pages. We never remove information (with very few exceptions). And being documentation, you don't risk regressions (or they are less dangerous than software regressions).