1The release criteria for libdrm is essentially "if you need a release, 2make one". There is no designated release engineer or maintainer. 3Anybody is free to make a release if there's a certain feature or bug 4fix they need in a released version of libdrm. 5 6When new ioctl definitions are merged into drm-next, we will add 7support to libdrm, at which point we typically create a new release. 8However, this is up to whoever is driving the feature in question. 9 10Follow these steps to release a new version of libdrm: 11 12 1) Bump the version number in configure.ac. We seem to have settled 13 for 2.4.x as the versioning scheme for libdrm, so just bump the 14 micro version. 15 16 2) Run autoconf and then re-run ./configure so the build system 17 picks up the new version number. 18 19 3) Verify that the code passes "make distcheck". Running "make 20 distcheck" should result in no warnings or errors and end with a 21 message of the form: 22 23 ============================================= 24 libdrm-X.Y.Z archives ready for distribution: 25 libdrm-X.Y.Z.tar.gz 26 libdrm-X.Y.Z.tar.bz2 27 ============================================= 28 29 Make sure that the version number reported by distcheck and in 30 the tarball names matches the number you bumped to in configure.ac. 31 32 4) Push the updated master branch with the bumped version number: 33 34 git push origin master 35 36 assuming the remote for the upstream libdrm repo is called origin. 37 38 5) Use the release.sh script from the xorg/util/modular repo to 39 upload the tarballs to the freedesktop.org download area and 40 create an announce email template. The script takes one argument: 41 the path to the libdrm checkout. So, if a checkout of modular is 42 at the same level than the libdrm repo: 43 44 ./modular/release.sh libdrm 45 46 This copies the two tarballs to freedesktop.org and creates 47 libdrm-2.4.16.announce which has a detailed summary of the 48 changes, links to the tarballs, MD5 and SHA1 sums and pre-filled 49 out email headers. Fill out the blank between the email headers 50 and the list of changes with a brief message of what changed or 51 what prompted this release. Send out the email and you're done! 52