Open Ocramius opened 6 years ago
We've been using release-X.Y.Z
since, well, the very first public release, and continued that into ZF2; Composer added a rule to allow the release-
prefix early on, because it was already our practice.
With the 2.5.0 release and breaking into components, we kept the release-X.Y.Z
format as we were able to maintain the sha1 compatibility with existing composer.lock
files if we did.
At the time, I made the following decision:
release-X.Y.Z
for components already in the ZF tree or derived from existing components (e.g., zend-router, which was derived via a git subtree split operation).X.Y.Z
for any new components.As such, we have >50% of our components currently using straight SemVer names, and around 50 or so on the old scheme.
We have a few options:
release-
tag names with those omitting the prefix. Sorting orders, duplication, etc. I have no idea how this would play with Packagist and Composer.Duplication of our tags should work quite okay, but I'll make sure that I ask first
Well, we strip release-
for legacy reasons (probably because you asked at some point if we can support your tags :P). And that isn't going to go away anytime soon. So basically, all your release-X.Y.Z
tags are just considered as X.Y.Z
tags. Adding proper Semver tags to those same references would probably result in unpredictable behavior as I am not sure how Composer would/could determine which X.Y.Z
has precedence.
As per https://github.com/Roave/BackwardCompatibilityCheck/issues/37#issuecomment-392429139 by @alcohol: