-
Notifications
You must be signed in to change notification settings - Fork 172
Making Releases
Aaron Skomra edited this page Sep 14, 2017
·
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''' or '''autogen.sh''', build and install the library. Verify that ''' pkg-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 tag '''git push origin libwacom-VERSION'''
- Scp the tarball to sourceforge. DealingWithSourceforge and then run '''scp libwacom-VERSION.tar.bz2 [email protected]:/home/frs/project/linuxwacom/libwacom'''
- Generate the git shortlog with '''git log --no-merges libwacom-0.4..libwacom-0.5 | git shortlog''', then add the NEWS section you added above.
- '''Sign off the email''' and send it to the Mailing lists
- Close all Sourceforge and 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.