Relevant mailing list discussion for the website part is available at [1]. [1]: https://mail.haskell.org/pipermail/xmonad/2020-February/015358.html
3.0 KiB
XMonad Maintainers
The XMonad Core Team
Release Procedures
When the time comes to release another version of XMonad and Contrib...
-
Create a release branch (e.g.,
release-0.XX
).This will allow you to separate the release process from main development. Changes you make on this branch will be merged back into
master
as one of the last steps. -
Update the version number in the
*.cabal
files and verify dependencies and documentation. This includes thetested-with:
field. -
Use the packdeps tool to ensure you have the dependency versions correct. If you need to update the version of a dependency then you should rebuild and retest.
-
Review documentation files and make sure they are accurate:
README.md
CHANGES.md
- and the
example-config.hs
in thexmonad-testing
repo
-
Generate the manpage:
cabal configure
with the-fgeneratemanpage
flag- Build the project
- Run the
generatemanpage
tool from the top level of this repo - Review the man page:
man -l man/xmonad.1
-
Tag the repository with the release version (e.g.,
v0.13
) -
Build the project tarballs (
cabal sdist
) -
Upload the packages to Hackage (
cabal upload
) -
Merge the release branches into
master
-
Update the website:
-
Generate and push haddocks with
xmonad-web/gen-docs.sh
-
Check that
tour.html
andintro.html
are up to date, and mention all core bindings
-
-
Update the topic for the IRC channel (
#xmonad
) -
Send the
announce-0.XX.txt
file to:- XMonad mailing list
- Haskell Cafe
Website and Other Accounts
-
The xmonad twitter is tended to by liskin.
-
The xmonad.org domain is owned by eyenx and the website itself is deployed via GitHub Pages. It can be updated by making a pull request against the xmonad-web repository.