"Here is a minor update to our library from 0.8.x to 0.9.0. - Oh, and it is breaking everything, because we changed the API."

o'rly?!

What on earth will happen on a major update?

Really, what is it with the fear of major release numbers? Just name it 1.0 and 2.0 if you break 1.0.

Better yet: just give it a new name. Thingy2 would totally do the job.

I think 0.x is supposed to be the exception to the major-versioning rule, because 0.x means you haven't done an official release yet, so everything is expected to be in state of constant pre-alpha flux. 1.x is the first reliable API version and any breaking changes after that should go to 2.x.

In reality... how many libraries out there stay at 0.8.x or 0.9.x forever... 😞

While we're at it, what's the distinction between 1.1.1 and 1.2.0?

@HollowKitty I see your point there. But a ton of libraries stay in 0.x. It seems there is a fear of major releases. I wonder why that is.