New Releases and API Stability
Developing smart contracts is hard, and a conservative approach towards dependencies is sometimes favored. However, it is also very important to stay on top of new releases: these may include bugfixes, or deprecate old patterns in favor of newer and better practices.
Here we describe when you should expect new releases to come out, and how this affects you as a user of OpenZeppelin Contracts.
OpenZeppelin Contracts follows a semantic versioning scheme.
OpenZeppelin Contracts has a 5 week release cycle. This means that every five weeks a new release is published.
At the beginning of the release cycle we decide which issues we want to prioritize, and assign them to a milestone on GitHub. During the next five weeks, they are worked on and fixed.
Once the milestone is complete, we publish a feature-frozen release candidate. The purpose of the release candidate is to have a period where the community can review the new code before the actual release. If important problems are discovered, several more release candidates may be required. After a week of no more changes to the release candidate, the new version is published.
Every several months a new major release may come out. These are not scheduled, but will be based on the need to release breaking changes such as a redesign of a core feature of the library (e.g. roles in 2.0). Since we value stability, we aim for these to happen infrequently (expect no less than six months between majors). However, we may be forced to release one when there are big changes to the Solidity language.
On the OpenZeppelin 2.0 release, we committed ourselves to keeping a stable API. We aim to more precisely define what we understand by stable and API here, so users of the library can understand these guarantees and be confident their project won’t break unexpectedly.
In a nutshell, the API being stable means if your project is working today, it will continue to do so. New contracts and features will be added in minor releases, but only in a backwards compatible way.
While the internal implementation of functions may change, their semantics and signature will remain the same. The domain of their arguments will not be less restrictive (e.g. if transferring a value of 0 is disallowed, it will remain disallowed), nor will general state restrictions be lifted (e.g.
If new functions are added to a contract, it will be in a backwards-compatible way: their usage won’t be mandatory, and they won’t extend functionality in ways that may foreseeable break an application (e.g. an
internal method may be added to make it easier to retrieve information that was already available).
This extends not only to
public functions, but also
internal ones: many contracts are meant to be used by inheriting them (e.g.
PullPayment, the different
Roles contracts), and are therefore used by calling these functions. Similarly, since all OpenZeppelin Contracts state variables are
private, they can only be accessed this way (e.g. to create new
ERC20 tokens, instead of manually modifying
_mint should be called).
private functions have no guarantees on their behavior, usage, or existence.
Finally, sometimes language limitations will force us to e.g. make
internal a function that should be
private in order to implement features the way we want to. These cases will be well documented, and the normal stability guarantees won’t apply.
Some of our Solidity libraries use
structs to handle internal data that should not be accessed directly (e.g.
Roles). There’s an open issue in the Solidity repository requesting a language feature to prevent said access, but it looks like it won’t be implemented any time soon. Because of this, we will use leading underscores and mark said
struct s to make it clear to the user that its contents and layout are not part of the API.
No events will be removed, and their arguments won’t be changed in any way. New events may be added in later versions, and existing events may be emitted under new, reasonable circumstances (e.g. from 2.1 on,
ERC20 also emits
While attempts will generally be made to lower the gas costs of working with OpenZeppelin Contracts, there are no guarantees regarding this. In particular, users should not assume gas costs will not increase when upgrading library versions.
The API stability guarantees may need to be broken in order to fix a bug, and we will do so. This decision won’t be made lightly however, and all options will be explored to make the change as non-disruptive as possible. When sufficient, contracts or functions which may result in unsafe behaviour will be deprecated instead of removed (e.g. #1543 and #1550).
Starting on version 0.5.0, the Solidity team switched to a faster release cycle, with minor releases every few weeks (v0.5.0 was released on November 2018, and v0.5.5 on March 2019), and major, breaking-change releases every couple months (with v0.6.0 scheduled for late March 2019). Including the compiler version in OpenZeppelin Contract’s stability guarantees would therefore force the library to either stick to old compilers, or release frequent major updates simply to keep up with newer Solidity releases.
Because of this, the minimum required Solidity compiler version is not part of the stability guarantees, and users may be required to upgrade their compiler when using newer versions of Contracts. Bugfixes will still be backported to older library releases so that all versions currently in use receive these updates.
You can read more about the rationale behind this, the other options we considered and why we went down this path here.