Releasing XCB Modules

(based on cairo's release process) (requires the maintainer to have a gpg key to sign the tag)

1. Update README

2. Update NEWS

   • git shortlog <last version>..
   • Skip any fixes to bugs that didn't exist in the last release
   • Skip any typos or similar cosmetic changes

3. Bump the package version in the top-level configure.ac

4. Commit changed README, NEWS, and configure.ac

   • git commit -m "Release <name> <version>"

5. check that all your changes are committed

   • git status must not show any uncommitted files and you must be on the master branch
   • git diff HEAD must not show anything

6. autoreconf -vfi && ./configure && make distcheck

7. Tag the repository

   • git tag -s -m "Release <name> <version>" <version>
   • verify with git verify-tag <version>

8. Compose the release mail (but don't send yet!)

   • template off of last release mail
     • replace version, README, NEWS
     • git tag and keysign
     • MD5 and SHA1 checksums + URL's of tarballs (md5sum, sha1sum)
     • note names of releasers

9. Push the master branch and the tag with git push origin master <version>

10. Copy the .gz and .bz2 tarballs to xcb.freedesktop.org:/srv/xcb.freedesktop.org/www/dist/ so they show up at http://xcb.freedesktop.org/dist/

11. Send the release mail to xorg and xcb lists

    • Subject: [ANNOUNCE] <name> <version>
    • To: xcb@lists.freedesktop.org, xorg-announce@lists.freedesktop.org, xorg@lists.freedesktop.org
    • don't forget to GPG-sign the email

12. Update the xcb wiki (main page, if necessary)

13. Bug Jamey Sharp and/or Julien Danjou to release a Debian package