@@ -206,12 +206,11 @@ If a new package fails to build because of missing system libraries we often ask
207### Upgrading GHC version
207### Upgrading GHC version
208The Dockerfile contains information on which GHC versions should be used. You
208The Dockerfile contains information on which GHC versions should be used. You
209−can modify it and push it to Github to trigger a DockerHub build. The nightly
209+can modify it and push it to Github to trigger a build. The nightly
210branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the
210branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the
211major version number (e.g., lts3 for lts-3.\*).
211major version number (e.g., lts3 for lts-3.\*).
213−Note that when starting a new LTS major release, you'll need to modify Docker
213+Note that when starting a new LTS major release, you'll need to modify `.github/workflows/image.yml` to add a new lts branch.
214−Hub to create a new Docker tag for the relevant branch name.
216Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.)
215Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.)
@@ -241,7 +240,7 @@ docker rm $(docker ps -a -q)
241docker rmi $(docker images -q)
240docker rmi $(docker images -q)
244−but `docker pull commercialhaskell/stackage:nightly` can also be run instead just to update the nightly image say.
243+but `docker pull ghcr.io/commercialhaskell/stackage/build:nightly` can also be run instead just to update the nightly image say.
246For a new GHC version you should also delete the ~~cache~~ .stack-work snapshot install directories on the stackage-build server to
245For a new GHC version you should also delete the ~~cache~~ .stack-work snapshot install directories on the stackage-build server to
247~~force all packages to be rebuilt~~ clear up some space. See: [issue#746](https://github.com/commercialhaskell/stackage/issues/746). Eg:
246~~force all packages to be rebuilt~~ clear up some space. See: [issue#746](https://github.com/commercialhaskell/stackage/issues/746). Eg:
@@ -555,8 +554,7 @@ Every 3-6 months, we make a new major release of LTS. The procedure we follow fo
555 relaxed upper bounds. There will likely be some hard decisions to be made
554 relaxed upper bounds. There will likely be some hard decisions to be made
556 regarding relaxing a bound versus keeping more packages. All of these changes
555 regarding relaxing a bound versus keeping more packages. All of these changes
557 occur on master and affect nightly.
556 occur on master and affect nightly.
558−4. Once the estimated date hits, push a new `ltsXX` branch and trigger Docker
557+4. Once the estimated date hits, push a new `ltsXX` and wait for the docker image build.
559− Hub to build a Docker image for the new release.
5605. Run the build procedure for the new LTS release.
5585. Run the build procedure for the new LTS release.
5616. After the LTS build completes, more aggressively prune upper bounds from
5596. After the LTS build completes, more aggressively prune upper bounds from
562 `build-constraints.yaml`.
560 `build-constraints.yaml`.