Describe pre-1.0 behavior in the compat section

[ChrisRackauckas]

No description provided.

[KristofferC]

I would write this as:

While the semver specification says that all versions with a major version of 0 (versions before 1.0.0) are incompatible with each other, we have decided to only apply that for when both the major and minor versions are zero. In other words, 0.0.1 and 0.0.2 are considered incompatible.
When the minor version is not zero, versions with the same minor versions are considered compatible, i.e. the two versions 0.2.1 and 0.2.3 are considered compatible. Version with a major version of 0 and different minor versions are not considered compatible, so the version 0.3.0 might have breaking changes from 0.2.0. To that end, the compat entry:

[compat]
Example = "0.0.1"

results in a versionbound on Example as [0.0.1, 0.02) (which is equivalent to only the version 0.0.1) and the compat entry

[compat]
Example = "0.2"

results in a versionbound on Example as [0.2.0, 0.3.0), (which is equivalent to all versions starting with 0.2).

[fredrikekre]

bors r+

[bors]

Build failed

• continuous-integration/travis-ci/push

[fredrikekre]

bors r+

[bors]

Build succeeded

• continuous-integration/appveyor/branch
• continuous-integration/travis-ci/push