summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2009-04-10 14:07:14 -0700
committerCarl Worth <cworth@cworth.org>2009-04-13 13:41:39 -0700
commit387b5be8e7efdb9aa2cfb8bb64b92fae69241f1b (patch)
tree6c3a1081a9ae7d77fa155c014e8639575991207d
parent121bd7ff7cfd9a43fbb61fa56f06ba2d2b55035e (diff)
Add a RELEASING file documenting the release process
Thanks to Jesse Barnes for the original recipe. (cherry picked from commit 6d345c49f693cc5cffaa00b94559d2afcb3a0864)
-rw-r--r--RELEASING32
1 files changed, 32 insertions, 0 deletions
diff --git a/RELEASING b/RELEASING
new file mode 100644
index 00000000..c4006c30
--- /dev/null
+++ b/RELEASING
@@ -0,0 +1,32 @@
+The process for releasing a new tarball is as follows:
+
+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)
+
+ $ vi configure.ac # bump version
+ $ git push origin # make sure you're on the release branch
+
+3. verify your module builds
+
+ $ make distcheck
+
+4. tag the release
+
+ $ git tag -m "Intel <ver> release" xf86-video-intel-<ver>
+
+5. run the release script (this should push the tag)
+
+ $ <path_to>/util/modular/release.sh driver xf86-video-intel-<last_ver> xf86-video-intel-<ver>
+
+6. edit the generated release message as needed and send it out
+
+ for major releases list added features and known limitations
+
+ for minor releases indicate which bugs were fixed and which
+ are still present
+
+7. throw a release party, you're done! :)