Making Releases

libwacom

This section describes how to do a new libwacom release. It assumes your meson build directory is builddir/.

Run this from a "clean" directory. If you have stale autotools files in your directory, this may result in weird errors

0. Update NEWS with an outline of changes since the last version
1. Change meson.build to reflect the new version number and commit: git commit -sm "libwacom VERSION" meson.build NEWS . You ''must not'' have uncommitted changes when releasing a new version.
2. Run sudo meson test -C builddir --no-rebuild to run all tests, including those requiring root. The --no-rebuild flag prevents rebuilding the code and having permission errors later.
3. Runmeson install -C builddir to install the library. Verify that pkg-config --modversion libwacom shows the new version
4. Run meson dist -C builddir/ (this also runs the test suite). Verify the name of the tarball (libwacom-VERSION.tar.bz2).
5. Tag the module: git tag -m "libwacom VERSION" --sign libwacom-VERSION . This will ask for your GPG password.
6. Push to the remote: git push origin master and for the tag git push origin libwacom-VERSION. Alternatively you could/should push to your fork and check the Actions tab in github to ensure the CI passes.
7. Use the release.sh script from xf86-input-wacom to copy the tarball to github. ./release.sh --github github_username:github_token . . See the other release procedures at linuxwacom's github for more information about the github token. To create a token with API and package write access, go here
8. Add the NEWS section you added above to the release description on Github.
9. Close all Github bugs that were fixed in this release by setting the status to "closed-fixed" and posting the following message: "Fix available in libwacom "

Note that it may take a while until the uploaded tarballs are available through the download links.