Outline release manager on-boarding instructions authored by Ben Gamari's avatar Ben Gamari
......@@ -96,3 +96,26 @@ The release manager will usually merge patches with `git cherry-pick`, so patche
The list of active (and defunct) [development branches](active-branches) is available. Note that currently **only administrators have privileges to perform disrupting changes** (such as deleting branches) to the repository.
## On-boarding release managers
The following is necessary when adding a new release manager:
* Ensure that they are in the ghc/release> group
* Ensure that their SSH key has been granted access to the `ghc` uploaders set of `downloads.haskell.org`
* Ensure that they GPG key has been cross-signed by at least one other release manager
* Ensure that their Hackage access has maintainer access to the [GHC core libraries](https://gitlab.haskell.org/ghc/ghc/-/blob/master/.gitlab/rel_eng/upload_ghc_libs.py?ref_type=heads#L109):
* `base`
* `ghc-bignum`
* `ghc-boot-th`
* `ghc-boot`
* `ghc-compact`
* `ghc-experimental`
* `ghc-heap`
* `ghc-internal`
* `ghc-prim`
* `ghc`
* `ghci`
* `integer-gmp`
* `template-haskell`