... | @@ -10,20 +10,6 @@ A few notes about GHC's issue tracker: |
... | @@ -10,20 +10,6 @@ A few notes about GHC's issue tracker: |
|
* We define one milestone for every minor release. However, issue targetting a milestone does not necessarily mean that the issue will be fixed in that release. New tickets are generally milestoned to the next major release. If a ticket remained unfixed when that milestone arrives, it is kicked to the next major release. If after three releases the ticket is still unfixed, its milestone is unset.
|
|
* We define one milestone for every minor release. However, issue targetting a milestone does not necessarily mean that the issue will be fixed in that release. New tickets are generally milestoned to the next major release. If a ticket remained unfixed when that milestone arrives, it is kicked to the next major release. If after three releases the ticket is still unfixed, its milestone is unset.
|
|
* A commit will automatically close an issue if it it contains a line which begins with text of the form `Closes #1234`. This is significantly more conservative than GitLab's default behavior, which auto-closes in response to a [much larger set](https://docs.gitlab.com/ee/administration/issue_closing_pattern.html) of patterns.
|
|
* A commit will automatically close an issue if it it contains a line which begins with text of the form `Closes #1234`. This is significantly more conservative than GitLab's default behavior, which auto-closes in response to a [much larger set](https://docs.gitlab.com/ee/administration/issue_closing_pattern.html) of patterns.
|
|
|
|
|
|
## Triage Rota
|
|
|
|
|
|
|
|
The current triage rota is split between @sheaf, @duog, @andreask, @mpickering, @wz1000 and @bgamari.
|
|
|
|
|
|
|
|
| Day | Triager |
|
|
|
|
| ------ | ------ |
|
|
|
|
| Monday | @wz1000 |
|
|
|
|
| Tuesday | @sheaf |
|
|
|
|
| Wednesday | @andreask |
|
|
|
|
| Thursday | @duog |
|
|
|
|
| Friday | @mpickering |
|
|
|
|
| Saturday | @bgamari |
|
|
|
|
| Sunday | @bgamari |
|
|
|
|
|
|
|
|
## Triage protocol
|
|
## Triage protocol
|
|
|
|
|
|
When a reporter opens a new issue they will generally only provide an issue description using one of the [provided templates](https://gitlab.haskell.org/ghc/ghc/tree/master/.gitlab/issue_templates). The triage process involves ensuring that the issue report is complete and filling in any missing metadata. To ensure that new issues are triaged, the issue templates apply the ~"triage needed" label to all new issues.
|
|
When a reporter opens a new issue they will generally only provide an issue description using one of the [provided templates](https://gitlab.haskell.org/ghc/ghc/tree/master/.gitlab/issue_templates). The triage process involves ensuring that the issue report is complete and filling in any missing metadata. To ensure that new issues are triaged, the issue templates apply the ~"triage needed" label to all new issues.
|
... | | ... | |