document release steps

I realized a lot of this is just in my bash history and stuff I've stumbled
over. I'm sure other people know this, I'm mostly just writing it down for
reference next time I need to tag a release.

I didn't add it to the table of contents or anything since I don't think
any users really care, but I can if people think it's useful.

Signed-off-by: Tycho Andersen <tycho@tycho.pizza>

docs/manual/releasing.rst

@@ -0,0 +1,47 @@
+===============
+Releasing Qtile
+===============
+
+Here is a short document about how to tag Qtile releases.
+
+1. create a "Release vX.XX.XX" commit. I like to thank all the contributors; I
+   find that list with something like:
+
+.. bash::
+
+   git log --oneline --no-merges --format=%an $(git describe --tags --abbrev=0)..HEAD | sort -u
+
+note that this can sometimes generate duplicates if people commit with slightly
+different names; I typically clean it up manually.
+
+Be sure that you GPG-sign (i.e. the ``-S`` argument to ``git commit``) this commit.
+
+2. Create a GPG-signed annotated tag (``git tag -a -s vX.XX.XX``); I usually just use
+   exactly the same commit message as the actual release commit above.
+
+3. Push your tag to qtile/qtile directly:
+
+.. bash::
+
+   git push origin vX.XX.XX
+
+4. Check the `Release action
+   <https://github.com/qtile/qtile/actions/workflows/release.yml>`_; the "Test
+   PyPI upload" action should build and upload the wheels to the test
+   environment. If this step breaks, you can delete your tag (``git push origin
+   :vX.XX.XX``), fix the bug, re-tag, and hopefully that will work.
+
+5. If the release worked, push to qtile/qtile master directly (``git push
+   origin master``).
+
+6. Create a new `Github release
+   <https://github.com/qtile/qtile/releases/new>`_; this is what will trigger
+   the actions in ``.github/workflows/release.yml`` to actually do the real pypi
+   upload.
+
+7. Make sure all of these actions complete as green. The release should show up
+   in a few minutes after completion here: https://pypi.org/project/qtile/
+
+8. send a mail to qtile-dev@googlegroups.com; I sometimes just use
+   git-send-email with the release commit, but a manual copy/paste of the
+   release notes into an e-mail is fine as well.