From abdc798eacc4cc210d440734ce0197b6b8dcfba6 Mon Sep 17 00:00:00 2001 From: plebhash <147345153+plebhash@users.noreply.github.com> Date: Wed, 4 Sep 2024 09:17:43 -0300 Subject: [PATCH] Update RELEASE.md Co-authored-by: jbesraa --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 819e85eda7..b74305945e 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -43,7 +43,7 @@ SemVer CI check would fail. Note that this does not apply to the `roles` and other crates in the repository. The global repository releases follow `X.Y.Z`, which is changed under some subjective criteria: -- any changes to `roles` are not taken into account, as to signify that they are mere PoCs are not suited for production scenarios. +- Changes in `roles` are not taken into account. `roles` crates are still in Proof of Concept phase and not production ready. - if the release is **only** fixing bugs on `protocols` or `utils`, then `Z` is bumped. - if the release is applying changes (breaking or non-breaking, which could also fix some bugs) to `protocols` or `utils`, then `Y` is bumped. - if the release marks a milestone where `protocols` is reaching a new level of maturity, then `X` is bumped.