mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
Document versioning behaviour
This commit is contained in:
parent
8951affb62
commit
fb856c3f8d
@ -6,6 +6,28 @@
|
||||
Installing Solidity
|
||||
###################
|
||||
|
||||
Versioning
|
||||
==========
|
||||
|
||||
Solidity versions follow `semantic versioning <https://semver.org>` and in addition to
|
||||
releases, **nightly development builds** are also made available. The nightly builds
|
||||
are not guaranteed to be working and despite best efforts they might contain undocumented
|
||||
and/or broken changes.
|
||||
|
||||
After a release is made, the patch version level is bumped, because we assume that only
|
||||
patch level changes follow. When changes are merged, the version should be bumped according
|
||||
to semver and the severity of the change. Finally, a release is always made with the version
|
||||
of the current nightly build, but without the ``prerelease`` specifier.
|
||||
|
||||
Example:
|
||||
- 0) the 0.4.0 release is made
|
||||
- 1) nightly build has a version of 0.4.1 from now on
|
||||
- 2) non-breaking changes are introduced - no change in version
|
||||
- 3) a breaking change is introduced - version is bumped to 0.5.0
|
||||
- 4) the 0.5.0 release is made
|
||||
|
||||
This behaviour works well with the version pragma.
|
||||
|
||||
Browser-Solidity
|
||||
================
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user