Ryan Scott <[email protected]> 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
signature.asc
Description: PGP signature
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
