Changing the versioning scheme

Our versioning scheme up to this point has been quite simple, we simply increment the patch number while keeping major and minor numbers at 0. At some point it will be appropriate to make a more significant bump.

For the proposals below, I'll use the letters X, Y and Z to be the major, minor and patch numbers. So a full version is X.Y.Z and we currently increment Z on each release.

We're fairly certain on one point: 1.0.0 should be tagged when we pass almost all GNU tests. It's probably not going to be 100%, but somewhere close to that. What the exact percentage will be, we'll have to decide later.

Also, we should be roughly following semver. According to semver though, 0.Y.Z is unstable and arbitrary. There are several things we could do until 1.0.0 (feel free to propose other schemes):

• Keep incrementing Z
• Let Y be the number of utils that pass all GNU tests and increment Z if there's no change in that number (proposed by @sylvestre)
• Let Y be the percentage of passing GNU tests divided by 10 (so 0.3.0 passes 30% of tests) and increment Z otherwise.

The last two options have the advantage that they convey some information about the state of the project, though that meaning will also need to be explained. They are also a bit more complicated.

Once we hit 1.0.0, we will have to change the scheme regardless of what option we pick.

What are your opinions?

cc @sylvestre @cakebaker

Start by reviewing the proposed versioning schemes and the GNU test milestone described in the issue. This discussion needs a maintainer decision on the scheme, its transition to 1.0.0, and how the chosen meaning will be documented; no files or tests are identified.