Files
xmonad/MAINTAINERS.md
Tomas Janousek 85787ce059 Automate and document releasing to Hackage
Pioneered in https://github.com/xmonad/X11, this adds automation for
Hackage releases and updates MAINTAINERS.md with simplified instruction
for the release procedure.

Related: https://github.com/xmonad/xmonad/issues/75
Related: https://github.com/xmonad/xmonad/issues/264
Related: https://github.com/xmonad/xmonad-contrib/issues/393
2021-07-24 18:13:11 +01:00

4.4 KiB

XMonad Maintainers

The XMonad Core Team

Hall of Fame (past maintainers/developers)

Release Procedures

When the time comes to release another version of xmonad and xmonad-contrib:

  1. Update the version number in all the *.cabal files and let the CI verify that it all builds together.

  2. Review documentation files and make sure they are accurate:

    If the manpage changes, wait for the CI to rebuild the rendered outputs.

  3. Check dependency bounds. In particular, packdeps can be used to check if any new versions are excluded by the upper bounds specified. Also, make sure that tested-with: covers several recent releases of GHC, and that .github/workflows/stack.yml tests with several recent revisions of Stackage LTS.

  4. Create a release on GitHub:

    CI will upload a release candidate to Hackage. Check again that everything looks good. To publish a final release, run the CI workflow once again with the correct version number:

    See haskell-ci-hackage.patch for details about the release infrastructure.

  5. Update the website:

  6. Post announcement to:

    See old announcements for inspiration.

Website and Other Accounts