1fe8aea9eSmrgThe process for releasing a new tarball is as follows: 2fe8aea9eSmrg 3fe8aea9eSmrg1. Make sure you have the latest build requirements installed: 4fe8aea9eSmrg 5fe8aea9eSmrg git://git.freedesktop.org/git/util/macros 6fe8aea9eSmrg git://git.freedesktop.org/git/util/modular 7fe8aea9eSmrg 8fe8aea9eSmrg2. Add relevant release notes to the NEWS files 9fe8aea9eSmrg 10fe8aea9eSmrg Skim the git log since the last release, and add notes in a 11fe8aea9eSmrg similar style to previous releases. 12fe8aea9eSmrg 13fe8aea9eSmrg For major releases list added features and known limitations. 14fe8aea9eSmrg 15fe8aea9eSmrg For minor releases indicate which bugs were fixed and which 16fe8aea9eSmrg are still present. 17fe8aea9eSmrg 18fe8aea9eSmrg 19fe8aea9eSmrg3. Update your module version (usually found in configure.ac) 20fe8aea9eSmrg 21fe8aea9eSmrg $ vi configure.ac # bump version 22fe8aea9eSmrg $ git commit 23fe8aea9eSmrg $ git push origin # make sure you're on the release branch 24fe8aea9eSmrg 25fe8aea9eSmrg4. Verify your module builds 26fe8aea9eSmrg 27fe8aea9eSmrg $ make distcheck 28fe8aea9eSmrg 29fe8aea9eSmrg5. Tag the release 30fe8aea9eSmrg 31fe8aea9eSmrg $ git tag -m "Intel <ver> release" <ver> 32fe8aea9eSmrg 33fe8aea9eSmrg6. Run the release script (this should push the tag) 34fe8aea9eSmrg 35fe8aea9eSmrg $ <path_to>/util/modular/release.sh driver <last_ver> <ver> 36fe8aea9eSmrg 37fe8aea9eSmrg7. Edit and send the generated release message. 38fe8aea9eSmrg 39fe8aea9eSmrg At the very least, add the release notes from the NEWS file. 40fe8aea9eSmrg 41fe8aea9eSmrg The message is generated as xf86-video-intel-<version>.announce 42fe8aea9eSmrg 43fe8aea9eSmrg For snapshots and release candidates, mail to: 44fe8aea9eSmrg 45fe8aea9eSmrg intel-gfx@lists.freedesktop.org 46fe8aea9eSmrg 47fe8aea9eSmrg For major releases also send to: 48fe8aea9eSmrg 49fe8aea9eSmrg xorg@lists.freedesktop.org 50fe8aea9eSmrg xorg-announce@lists.freedesktop.org 51fe8aea9eSmrg 52fe8aea9eSmrg8. Throw a release party, you're done! :) 53