From 54e9889e93595b147a4c40e29d8a1adcc96c2dba Mon Sep 17 00:00:00 2001 From: Mek Stittri Date: Thu, 13 Jun 2019 08:52:43 -0700 Subject: [PATCH] Change SLA to target SLO for bugs and defects --- doc/development/contributing/issue_workflow.md | 4 ++-- 1 file 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) |