-
Notifications
You must be signed in to change notification settings - Fork 172
Making Releases
Aaron Skomra edited this page Jul 17, 2019
·
14 revisions
This section describes how to do a new libwacom release.
- Update
NEWS
with an outline of changes since the last version - Change LIBWACOM_LT_VERSION according to the directions in configure.ac
- Change configure.ac to reflect the new version number and commit:
git commit -sm "libwacom VERSION" configure.ac NEWS
. You ''must not'' have uncommitted changes when releasing a new version. - Run
autoreconf -iv
orautogen.sh
, build and install the library. Verify thatpkg-config --modversion libwacom
shows the new version - Run
make distcheck
. Verify the name of the tarball (libwacom-VERSION.tar.bz2). - Tag the module:
git tag -m "libwacom VERSION" -s libwacom-VERSION
- Push to the remote:
git push origin master
and for the taggit push origin libwacom-VERSION
- Use the release.sh script 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. - Add the NEWS section you added above to the release description on Github.
- 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.