GitLab conventions

[Ben Gamari]

Hi everyone,

Today I have been working on better documenting our conventions under
GitLab. This has resulted in a handful of documents:

 * A gitlab/issues wiki page [1], describing our triage and issue
   resolution workflow

 * A gitlab/merge-requests wiki page [2], describing our patch backport
   workflow

 * issue and merge request templates (e.g. [3] and [4]), which will be used by
   authors of issues and MR, respectively.

If you frequent GHC's issue tracker it may be a good idea to look over
the triage guide [1] to make sure you understand the implications of our
many labels.

Also, on the behest of Simon I propose that we start using a comment
convention to note the addition of tests on issues (replacing Trac's
"Test Case" field). Specifically, I suggest that a comment containing a
line beginning with the token "Testsuite-tests:" followed by a series of
comma-separated strings denote a set of test-cases for the issue.
I have documented this here [5]

If there is consensus that this is a sensible and worthwhile convention
I will add these comments for the issues imported from Trac next week.

Cheers,

- Ben


[1] https://gitlab.haskell.org/ghc/ghc/wikis/gitlab/issues
[2] https://gitlab.haskell.org/ghc/ghc/wikis/gitlab/merge-requests
[3] https://gitlab.haskell.org/ghc/ghc/blob/master/.gitlab/issue_templates/bug.md
[4] https://gitlab.haskell.org/ghc/ghc/blob/master/.gitlab/merge_request_templates/merge-request.md 
[5] https://gitlab.haskell.org/ghc/ghc/wikis/gitlab/issues#marking-an-issue-as-resolved
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190401/89b507f8/attachment.sig>