For Developers: Making Releases

This section describes how to do a new input-wacom release.

0. Merge master into all current branches, and then merge those branches into master. Use the '--no-ff' option with 'git merge' to force a commit message.
1. Change configure.ac to reflect the new version number and commit: git commit -sm "input-wacom VERSION" configure.ac. You must not have uncommitted changes when releasing a new version.
2. Tag the module: git tag -m "input-wacom VERSION" -s v(VERSION EX: 1.0.0). You will use your PGP key for this step. (This step is necessary to get the modinfo version (eg. v2.00-0.37.0.11.gd0b76d0) correct.)
3. Run make dist. Verify the name of the tarball (input-wacom-VERSION.tar.bz2). If this is a clean clone of the repository, you will need to first run autogen.sh to generate the Makefile. It is also possible you may need to run make distclean if something goes wrong with make dist.
4. Build, install, and load the driver from the tarball.
5. Verify the version number of the loaded driver with modinfo wacom | grep version and cat /sys/module/wacom/version.
6. Push to the remote: git push origin master.
7. By default, the git push command doesn’t transfer tags to remote servers. Push the tag to the remote: git push origin v(VERSION).
8. In the actions tab of the input-wacom repository watch for the tagged release workflow to start and finish successfully.
9. Summarize the new features in this release and add it to the release description on Github.
10. Download the (input-wacom-VERSION.tar.bz2) and sign it (gpg -b input-wacom-VERSION.tar.bz2). Upload the resulting .tar.bz2.sig file to the release assets.
11. Close all Github bugs that were fixed in this release and which are fixed in an upstream Linux release by setting the status to "closed-fixed" and posting the following message: "Fix available in Linux and input-wacom "