-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Address feedback on stable versioning
Signed-off-by: Morgan Tocker <[email protected]>
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,7 +35,7 @@ best protect our users. | |
|
||
#### Policy for master-only vulnerabilities | ||
|
||
If a security vulnerability only affects master, but not a stable release (i.e. Vitess 5) then the following process will apply: | ||
If a security vulnerability affects master, but not a currently supported branch, then the following process will apply: | ||
|
||
* The fix will land in master. | ||
* A courtesy email will be sent to [[email protected]](https://groups.google.com/forum/#!forum/vitess) along with a posted notice in #developers on Slack. | ||
|
@@ -49,7 +49,7 @@ If a security vulnerability affects only a stable release which is no longer und | |
|
||
#### Policy for supported releases | ||
|
||
If a security vulnerability affects supported branches (i.e. Vitess 5), then a Fix Lead will be appointed and the full security process as defined below will apply. | ||
If a security vulnerability affects supported branches, then a Fix Lead will be appointed and the full security process as defined below will apply. | ||
|
||
### Fix Development Process | ||
|
||
|