On 01.09.2024 at 09:16, Mike Schinkel wrote: > One of the benefits for users when software authors strictly follow SemVer is > that automated tooling can decide if an automatic upgrade should be safe. > Depending on out-of-band information to convey BC breakage can result in > those who use automatic upgrades to see unexpected failures en masse since > automated tooling won't look at bespoke, non-standard labels when deciding. > > If enough software authors choose to be less strict about SemVer it could > have the fallout that many people decide it is just too risky to use > automated tooling. Once bitten, twice shy. > > One approach I have seen on other projects take is they retract the versions > with BC breakage and then release an update reversing the breakage.
What does "retract" mean in this context? I mean, we can delete the tag, remove the download from php.net – but the version has already been released, and might be used in the wild. We already have the "problem" that we tag on Tuesdays, but release on Thursdays, but you find builds from Wednesdays in Linux distros. Christoph
