twin/xmonad
1
0
Fork 0
mirror of https://github.com/xmonad/xmonad.git synced 2025-07-31 04:01:52 -07:00
Code Issues Packages Projects Releases Wiki Activity
Files
c2a1a3c0a6396d83b92c4efe1bd872fb3c701d61
xmonad/MAINTAINERS.md
Tomas Janousek b198b80559 README: Long overdue update 
* add logo and badges to make it prettier
* revamp installation sections
* update xmonad-contrib reference and move upwards
* drop other useful programs, this is in download.html
* add new Contributing section

Fixes: https://github.com/xmonad/xmonad/issues/199
2021-10-23 00:17:30 +01:00

4.5 KiB
Raw Blame History

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