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 @@ -83,8 +83,6 @@ The goal is to create or backport all needed PRs in this step so that the list o

1. Make sure `cabal-version` of Cabal and Cabal-syntax is *not* the latest cabal file format version and that it is within the backwards compat range, which extends to 5 years back (bump, to give a good example to cabal users, only during a major release, never minor). Look at the [file format changelog](https://cabal.readthedocs.io/en/stable/file-format-changelog.html) to see which `cabal-version` was released five years ago (the SPDX License List version gives away the date).

2. Check that language extensions are registered for the latest GHC version with `which ghc-x.y.z | xargs cabal run ghc-supported-extensions`.

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.
Expand Down