Skip to content

Latest commit

 

History

History
146 lines (93 loc) · 5.35 KB

MAINTAINERS.md

File metadata and controls

146 lines (93 loc) · 5.35 KB

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. Update the website:

  4. Make sure that tested-with: covers several recent releases of GHC, that .github/workflows/haskell-ci.yml had been updated to test all these GHC versions and that .github/workflows/stack.yml tests with several recent revisions of Stackage LTS.

  5. Trigger the Haskell-CI workflow and fill in the candidate version number. This will upload a release candidate to Hackage.

    Check that everything looks good. If not, push fixes and do another candidate. When everything's ready, create a release on GitHub:

    CI will automatically upload the final release to Hackage.

    See haskell-ci-hackage.patch for details about the Hackage automation.

  6. Post announcement to:

    See old announcements (even older) for inspiration.

  7. Trigger xmonad-docs build to generate and persist docs for the just released version:

  8. Bump version for development (add .9) and prepare fresh sections in CHANGES.md.

Website and Other Accounts