@@ -402,3 +402,25 @@ nightly build in order to move forward with getting the latest versions of
402packages compatible with the new GHC release.
402packages compatible with the new GHC release.
404[GHC upgrade note]: https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md#upgrading-to-a-new-ghc-version
404[GHC upgrade note]: https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md#upgrading-to-a-new-ghc-version
406+## New LTS major bump
408+Every 3-6 months, we make a new major release of LTS. The procedure we follow for this is:
410+1. Write a blog post on stackage.org announcing the intent to cut a major
411+ release. Give an estimated date two weeks in the future from the publication
413+2. Spread the blog post on social media and mailing lists as much as possible.
414+3. Expect maintainers to send significant requests for added packages and
415+ relaxed upper bounds. There will likely be some hard decisions to be made
416+ regarding relaxing a bound versus keeping more packages. All of these changes
417+ occur on master and affect nightly.
418+4. Once the estimated date hits, push a new `lts-XX` branch and trigger Docker
419+ Hub to build a Docker image for the new release.
420+5. Run the build procedure for the new LTS release.
421+6. After the LTS build completes, more aggressively prune upper bounds from
422+ `build-constraints.yaml`.
423+7. Once both (5) and (6) are done, publish a new blog post on stackage.org
424+ announcing the new LTS and Nightly, with links to the change pages on
425+ stackage.org. Include a reminder that requests for packages to be added to LTS
426+ may be made on commercialhaskell/lts-haskell.