diff options
| author | Andrew Newdigate <andrew@gitlab.com> | 2017-07-25 13:09:54 +0300 |
|---|---|---|
| committer | Andrew Newdigate <andrew@gitlab.com> | 2017-07-25 13:09:54 +0300 |
| commit | 309fd761adc719d4091df26c147dd0896a463d32 (patch) | |
| tree | d9fa8be0fdd091498a7e4e11762bad908a0b3be7 /CONTRIBUTING.md | |
| parent | 97ccfd66cf4e00d77322bd74682399b18a771141 (diff) | |
Update CONTRIBUTING.md
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ef781d45f..1344126de 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -81,7 +81,7 @@ spawn it's own issue. These issues should generally not stay open for more than 1. The Gitaly team uses a weekly Wednesday-Wednesday iteration with retrospectives every second week. 1. Work for the cycle should be assigned to the [appropriate Infrastructure Deliverable](https://gitlab.com/gitlab-org/gitaly/milestones/) milestone and tagged with the ~"Infrastructure Deliverable" label. - Please **do not assign ~Conversation issues** to the weekly infrastructure deliverable milestone or the ~"Infrastructure Deliverable" label. - - ~Conversations are ongoing work-streams while ~"Infrastructure Deliverable" issues should be closed by the upcoming milestone. + - ~"Conversation"s are ongoing work-streams while ~"Infrastructure Deliverable" issues should be closed by the upcoming milestone. 1. To keep track of slipping issues, items which we have been unable to complete by the infrastructure deliverable milestone should be moved over to the next milestone and marked with ~"Moved:x1", ~"Moved:x2", ~"Moved:x3" etc ## Reviews and Approvals |