diff options
| author | Fabio Busatto <fabio@gitlab.com> | 2018-06-20 18:13:41 +0300 |
|---|---|---|
| committer | Fabio Busatto <fabio@gitlab.com> | 2018-06-20 18:13:41 +0300 |
| commit | 4c77257a33867f7532b134be5ee49a269341e072 (patch) | |
| tree | 7b85dc47072b742c22f891d9fd912ea8836db875 /PROCESS.md | |
| parent | 7b1c34732317d9df8d17bbd85aa26a1c02623156 (diff) | |
Copyedits
Diffstat (limited to 'PROCESS.md')
| -rw-r--r-- | PROCESS.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md index c730cb918d9..2c081a0cecc 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -255,7 +255,7 @@ When a regression is found: 1. Schedule the issue in order to get it fixed as soon as possible, based on severity and priority, following these guidelines: - If the regression is ~S1 or ~S2, set the current milestone - If the regression was introduced in a RC of the current release, label with ~Deliverable - - If the regression was introduced in the previos release, label with ~"Next Patch Release" + - If the regression was introduced in the previous release, label with ~"Next Patch Release" - If the regression is ~S3 or ~S4, it can be scheduled for later milestones When a new issue is found, the fix should start as soon as possible. You can |