With the current versioning scheme YY.N it is difficult to figure out when a release breaks the public API or not.

Could we move to semantic versioning for packaging?

Scanning through the change log, many release appear to be not breaking anything, it seems? I am using packaging in several libraries and I need to be able to specify a stable range of acceptable versions without being unnecessarily restrictive to avoid dependency conflicts.