@@ -337,3 +337,24 @@ errors for builds, tests and benchmarks.
337337
3383381. Add public ssh key to `~/.ssh/authorized_keys` on build server
3393392. Add to fpco/stackage project.
340+
341+## Dealing with a new GHC release
342+
343+As mentioned in the [GHC upgrade note], the major impact of a new GHC release
344+is on the packages that are causing upper bounds to be put in place. In order
345+to minimise out-of-date breakage and allow maintainers to have a solid chance
346+of getting their packages into the newest LTS, we try to do the following:
347+
348+Make an early announcement (in the form of a blog post, typically) of the new
349+GHC release on the nightly build and the planned deadline for the new LTS release.
350+Make it clear, that in the time coming up to this, we hope package maintainers
351+will upgrade their packages to allow for the new GHC release.
352+
353+We prefer to prune packages causing upper bounds constraints **after** the LTS
354+release to allow the maximum amount of packages to get into the newest LTS.
355+
356+After the first LTS release, the package pruning process may begin in order to
357+move forward with getting the latest versions of packages compatible with the
358+new GHC release.
359+
360+[GHC upgrade note]: https://github.com/fpco/stackage/blob/master/MAINTAINERS.md#upgrading-to-a-new-ghc-version