Version 0.* and Semantic Versioning

[jtaylor100]

When using this library with a dependency constraint in composer such as ^0.4.1, newer versions such as 0.5.0 do not match this constraint (unlike a constraint such as ^1.4.1 and a version such as 1.5.1 which would match).

This is due to this rule in the semantic versioning spec:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

So the question I have to the maintainer is: would you consider the public API of this library stable? Does the choice of the 0.* version numbers fit with the rule above? Or can the rule be safely ignored here?

[juliangut]

Hi @jtaylor100

I can confirm this library is following semver, but as long as it is in version 0.x composer ^ behaves differently (you could be using ~ instead)

So I assume what you're asking is for us to finally release version v1.0 if we think the library is stable enough

In my opinion it is and we could release it as the library has been in use for long without any API changes, we'll discuss it internally in the team

[jtaylor100]

Thank you @juliangut