Making Releases - linuxwacom/libwacom GitHub Wiki

This page documents the release process for libwacom maintainers. It assumes your meson build directory is builddir/.

Start from a clean working tree with no uncommitted changes.

  1. Update NEWS with an outline of changes since the last version.
  2. Update the version number in meson.build and commit: git commit -sm "libwacom VERSION" meson.build NEWS
  3. Run the test suite including root-only tests: sudo meson test -C builddir --no-rebuild. The --no-rebuild flag prevents rebuilding as root and avoids permission problems afterwards.
  4. Install and verify: meson install -C builddir, then pkg-config --modversion libwacom should show the new version.
  5. Create the distribution tarball: meson dist -C builddir/. This also runs the test suite. Verify the tarball name is libwacom-VERSION.tar.bz2.
  6. Tag the release: git tag -m "libwacom VERSION" --sign libwacom-VERSION
  7. Push to the remote: git push origin master and git push origin libwacom-VERSION. Alternatively, push to your fork first and check the GitHub Actions CI before pushing to the main repository.
  8. Upload the tarball to GitHub using the release.sh script from xf86-input-wacom: ./release.sh --github github_username:github_token . See the xf86-input-wacom release procedures for details on creating a GitHub API token with write access. Create tokens here.
  9. Add the NEWS section to the release description on GitHub.
  10. Close fixed issues on GitHub with the message "Fix available in libwacom VERSION".

It may take a while for the uploaded tarballs to become available through the download links.