summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2009-05-12 11:45:03 -0700
committerCarl Worth <cworth@cworth.org>2009-05-12 11:46:17 -0700
commitb1f5cc3349f6811ff4d8dc64cc291788d6726372 (patch)
tree30b66b2460ef7c1b12f93273ba3c1f377c9469f1 /RELEASING
parentf16ee218845ec48940ea457b921d34896d80a807 (diff)
RELEASING: Better instructions for where to send announcements
The xorg-announce list doesn't need to hear about development snapshots and release candidates. The intel-gfx list is good for that.
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING13
1 files changed, 12 insertions, 1 deletions
diff --git a/RELEASING b/RELEASING
index 93761101..2196c8fd 100644
--- a/RELEASING
+++ b/RELEASING
@@ -33,8 +33,19 @@ The process for releasing a new tarball is as follows:
$ <path_to>/util/modular/release.sh driver <last_ver> <ver>
-7. Edit the generated release message as needed and send it out
+7. Edit and send the generated release message.
At the very least, add the release notes from the NEWS file.
+ The message is generated as xf86-video-inte-<version>.announce
+
+ For snapshots and release candidates, mail to:
+
+ intel-gfx@lists.freedesktop.org
+
+ For major releases also send to:
+
+ xorg@lists.freedesktop.org
+ xorg-announce@lists.freedesktop.org
+
8. Throw a release party, you're done! :)