GitLab conventions

[Ben Gamari]

Ryan Scott <ryan.gl.scott at gmail.com> writes:

> Thanks! The updated information is now on
> https://gitlab.haskell.org/ghc/ghc/wikis/gitlab/merge-requests, for those
> who are curious:
>
>> While the release manager can perform the backport on your behalf, it is
> appreciated if you open a merge request with the backported patches
> yourself.
>
> One further question: if a patch (that is intended to be backported) first
> lands on master, is it considered good practice to leave the corresponding
> issue open until the backport happens, similar to Trac's "merge" status? Or
> is this practice obsolete in the new label-based workflow?
>
Indeed this should be documented (which I have done): the ticket should
remain open. To identify backports I look at open tickets bearing the
"backport needed" label.

Cheers,

- Ben
-------------- 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/20190402/0696d4fb/attachment.sig>