Skip to content

Compare: Making a release

Showing with 0 additions and 2 deletions.
  1. +0 −2 Making-a-release.md
2 changes: 0 additions & 2 deletions Making-a-release.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -85,8 +85,6 @@ The goal is to create or backport all needed PRs in this step so that the list o

3. Check for new `ghc` options: `comm -13 <(ghc-oldver --show-options | sort) <(ghc-newver --show-options | sort) | grep '^-f'`. Note that these can pop up in `ghc` minor versions! Options that do not change generated artifacts (most of them do, so cabal assumes the worst) need to be recorded in `Cabal/src/Distribution/Simple/Program/GHC.hs`. Add such options in `simpleFilters` if they take no parameters or integer parameters, otherwise in `argumentFilters`.

4. Run `cabal outdated` in `./Cabal`, `./cabal-install`, `./Cabal-syntax`, `/Cabal-hooks`, `./hooks-exe` and `./cabal-install-solver` and update as needed.

5. Commit the changes to `master`, then backport them to the release branch. You may also want to backport to still-supported branches. (e.g. if we are releasing `3.12`, we will commit to `master`, backport to `3.12` *and* backport to `3.10`.)

#### C.2 CHANGELOGs
Expand Down