diff options
| author | Carl Worth <cworth@cworth.org> | 2009-04-15 16:44:11 -0700 |
|---|---|---|
| committer | Carl Worth <cworth@cworth.org> | 2009-04-15 16:44:11 -0700 |
| commit | 3fd5a1ecd1d5140ae07ccc279298bcadd515e97f (patch) | |
| tree | 141b708ac6dd3643443fb135b8a2e897d578db8f | |
| parent | e1cace16a6130dcdd93965d2329a349d49200fa6 (diff) | |
RELEASING: Update instructions to reflect some minor process improvements
We've added a NEWS file now, so that needs to be updated for each release.
We're also now using tag names of just <version> rather than
xf86-video-intel-<version>.
| -rw-r--r-- | RELEASING | 34 |
1 files changed, 21 insertions, 13 deletions
@@ -1,32 +1,40 @@ The process for releasing a new tarball is as follows: -1. make sure you have the latest build requirements installed: +1. Make sure you have the latest build requirements installed: git://git.freedesktop.org/git/util/macros git://git.freedesktop.org/git/util/modular -2. update your module version (usually found in configure.ac) +2. Add relevant release notes to the NEWS files + + Skim the git log since the last release, and add notes in a + similar style to previous releases. + + For major releases list added features and known limitations. + + For minor releases indicate which bugs were fixed and which + are still present. + + +3. Update your module version (usually found in configure.ac) $ vi configure.ac # bump version $ git push origin # make sure you're on the release branch -3. verify your module builds +4. Verify your module builds $ make distcheck -4. tag the release - - $ git tag -m "Intel <ver> release" xf86-video-intel-<ver> +5. Tag the release -5. run the release script (this should push the tag) + $ git tag -m "Intel <ver> release" <ver> - $ <path_to>/util/modular/release.sh driver xf86-video-intel-<last_ver> xf86-video-intel-<ver> +6. Run the release script (this should push the tag) -6. edit the generated release message as needed and send it out + $ <path_to>/util/modular/release.sh driver <last_ver> <ver> - for major releases list added features and known limitations +7. Edit the generated release message as needed and send it out - for minor releases indicate which bugs were fixed and which - are still present + At the very least, add the release notes from the NEWS file. -7. throw a release party, you're done! :) +8. Throw a release party, you're done! :) |