Skip to content

Commit

Permalink
Merge pull request #1154 from plebhash/global-release-docs
Browse files Browse the repository at this point in the history
global release docs
  • Loading branch information
plebhash authored Sep 4, 2024
2 parents aba4182 + 03c131b commit 7dd0478
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,6 @@ Things to take into account while writing a changelog:
- Breaking changes.
- Notable changes.


## Release Process

Try to constrain each development cycle to a fixed time period, after which a
Expand All @@ -35,18 +34,19 @@ Usually the release process is as follows:
5. Create a new tag for the release branch.
6. Publish the release.


## Versioning

Protocol and Utils crates follow SemVer 2.0.0. The version number is stored in
Crates under `protocols` and `utils` workspaces follow SemVer 2.0.0. The version number is stored in
the `Cargo.toml` file of each crate. If a breaking change is introduced to one
of the crates, the version number must be updated accordingly, otherwise a
SemVer CI check would fail. Note that this does not apply to the `roles` and
other crates in the repository.

The general SRI version does not follow any SemVer rules. You can track the
releases on Github Releases in the repository.

The global repository releases follow `X.Y.Z`, which is changed under some subjective criteria:
- Changes in `roles` are not taken into account. `roles` crates are still in Proof of Concept phase and not production ready.
- If a release includes only bug fixes in `protocols` and/or `utils`, then `Z` is bumped.
- If a release includes breaking and/or non-breaking changes to `protocols` and/or `utils`, then `Y` is bumped.
- If a release marks a milestone i.e., `protocols` is reaching a new maturity level, then `X` is bumped.

## Tags and Branches

Expand Down

0 comments on commit 7dd0478

Please sign in to comment.