refactor: reword to pre-releases

This commit is contained in:
marco-ippolito 2024-03-26 15:44:10 +01:00 committed by Wes Todd
parent 4e3f95c0ea
commit 51a76366e3
2 changed files with 7 additions and 7 deletions

View File

@ -79,10 +79,10 @@ non-patch flow.
### Pre-release Versions
Beta releases are made from a proposal branch. The version number should be
incremented to the next minor version with a `-beta` suffix. For example, if the
next release is `5.0.1`, the beta release would be `5.0.1-beta.0`. The beta
release should be considered unstable and not suitable for production use.
Alpha and Beta releases are made from a proposal branch. The version number should be
incremented to the next minor version with a `-beta` or `-alpha` suffix.
For example, if the next beta release is `5.0.1`, the beta release would be `5.0.1-beta.0`.
The pre-releases should be considered unstable and not suitable for production use.
### Patch flow

View File

@ -31,9 +31,9 @@ the module.
## Pre-release Versions
Beta releases should be considered unstable and **not suitable for production use**.
Vulnerabilities found in beta releases should be reported according to the [Reporting a Bug](#reporting-a-bug) section.
Due to the unstable nature of the branch it is not garanteed that the fix will be released in the next beta release.
Alpha and Beta releases should be considered unstable and **not suitable for production use**.
Vulnerabilities found in pre-releases should be reported according to the [Reporting a Bug](#reporting-a-bug) section.
Due to the unstable nature of the branch it is not garanteed that the fix will be released in the next pre-release.
## Disclosure Policy