Openzeppelin-contracts: How does the versioning work?
Do you follow the MAJOR.MINOR.PATCH semantic? Because if yes, then 1.7.0 breaks backwards compatibility.
marti-1
All 5 comments
https://github.com/OpenZeppelin/zeppelin-solidity/blob/master/README.md#getting-started
Note that OpenZeppelin does not currently follow semantic versioning. You may encounter breaking changes upon a minor version bump.
vidorge
on 23 Feb 2018
What is the reason for _not_ following Semver?
Qqwy
on 23 Feb 2018
Can someone please expand on this issue?
Not following Semantic Versioning goes against a (near) industry-wide standard and therefore the principle of least surprise. Most automatic tooling will treat OpenZeppelin's versions improperly, resulting in software that breaks, or worse, malformed smart contracts that get deployed.
Qqwy
on 10 Mar 2018
Dear maintainers of OpenZeppelin; we are still waiting for an answer. Please respond at your earliest convenience.
Qqwy
on 3 Apr 2018
the reasoning is basically: we want to feel free to make breaking changes often. We should be in 0.x.y but it's too late for that.
we updated the installation instructions to save the exact version instead of the semver expression, so it shouldn't cause unintended upgrades
moving to semver is planned in the future, but I'm not sure what that timeline is
shrugs
on 3 Apr 2018
Related issues
Flash-Git
路
3Comments
golivax
路
4Comments
mswezey23
路
4Comments
rstormsf
路
4Comments
spalladino
路
4Comments
Most helpful comment
What is the reason for _not_ following Semver?