summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMek Stittri <mstittri@gitlab.com>2019-06-13 08:52:43 -0700
committerMek Stittri <mstittri@gitlab.com>2019-06-13 08:52:43 -0700
commit54e9889e93595b147a4c40e29d8a1adcc96c2dba (patch)
treebe2a7337666e4dd9ccaca20d1fa551264215ed1b
parent7291484d313f8f999e7f2c07978ca855fd04f1c1 (diff)
downloadgitlab-ce-target-slo-defects.tar.gz
Change SLA to target SLO for bugs and defectstarget-slo-defects
-rw-r--r--doc/development/contributing/issue_workflow.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md
index e3a1dc711fd..0396f7ebc45 100644
--- a/doc/development/contributing/issue_workflow.md
+++ b/doc/development/contributing/issue_workflow.md
@@ -163,9 +163,9 @@ or ~"Stretch". Any open issue for a previous milestone should be labeled
Priority labels help us define the time a ~bug fix should be completed. Priority determines how quickly the defect turnaround time must be.
If there are multiple defects, the priority decides which defect has to be fixed immediately versus later.
-This label documents the planned timeline & urgency which is used to measure against our actual SLA on delivering ~bug fixes.
+This label documents the planned timeline & urgency which is used to measure against our target SLO on delivering ~bug fixes.
-| Label | Meaning | Defect SLA (applies only to ~bug and ~security defects) |
+| Label | Meaning | Target SLO (applies only to ~bug and ~security defects) |
|-------|-----------------|----------------------------------------------------------------------------|
| ~P1 | Urgent Priority | The current release + potentially immediate hotfix to GitLab.com (30 days) |
| ~P2 | High Priority | The next release (60 days) |