aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDamien Lespiau2015-03-19 11:27:31 -0500
committerDamien Lespiau2015-03-20 10:55:23 -0500
commit992940ca645f8dcda24015770d48afad0fd95b9d (patch)
tree7e4920773e4b88852c419994133d5ba2e7d31f17 /RELEASING
parent8f245b777b21e8c0151f9a254a56a7cb23b66d15 (diff)
downloadexternal-libdrm-992940ca645f8dcda24015770d48afad0fd95b9d.tar.gz
external-libdrm-992940ca645f8dcda24015770d48afad0fd95b9d.tar.xz
external-libdrm-992940ca645f8dcda24015770d48afad0fd95b9d.zip
RELEASING: Fix the step numbering
v2: Really fix the numbering (Emil Velikov) Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING12
1 files changed, 6 insertions, 6 deletions
diff --git a/RELEASING b/RELEASING
index e17dbea2..203b88bb 100644
--- a/RELEASING
+++ b/RELEASING
@@ -13,14 +13,14 @@ Follow these steps to release a new version of libdrm:
13 modifications. You're probably in a good state if both "git diff 13 modifications. You're probably in a good state if both "git diff
14 HEAD" and "git log master..origin/master" give no output. 14 HEAD" and "git log master..origin/master" give no output.
15 15
16 3) Bump the version number in configure.ac. We seem to have settled 16 2) Bump the version number in configure.ac. We seem to have settled
17 for 2.4.x as the versioning scheme for libdrm, so just bump the 17 for 2.4.x as the versioning scheme for libdrm, so just bump the
18 micro version. 18 micro version.
19 19
20 4) Run autoconf and then re-run ./configure so the build system 20 3) Run autoconf and then re-run ./configure so the build system
21 picks up the new version number. 21 picks up the new version number.
22 22
23 5) (optional step, release.sh will make distcheck for you, but it can be 23 4) (optional step, release.sh will make distcheck for you, but it can be
24 heart warming to verify that make distcheck passes) 24 heart warming to verify that make distcheck passes)
25 25
26 Verify that the code passes "make distcheck". Running "make 26 Verify that the code passes "make distcheck". Running "make
@@ -36,20 +36,20 @@ Follow these steps to release a new version of libdrm:
36 Make sure that the version number reported by distcheck and in 36 Make sure that the version number reported by distcheck and in
37 the tarball names matches the number you bumped to in configure.ac. 37 the tarball names matches the number you bumped to in configure.ac.
38 38
39 6) Commit the configure.ac change and make an annotated tag for that 39 5) Commit the configure.ac change and make an annotated tag for that
40 commit with the version number of the release as the name and a 40 commit with the version number of the release as the name and a
41 message of "libdrm X.Y.Z". For example, for the 2.4.16 release 41 message of "libdrm X.Y.Z". For example, for the 2.4.16 release
42 the command is: 42 the command is:
43 43
44 git tag -a 2.4.16 -m "libdrm 2.4.16" 44 git tag -a 2.4.16 -m "libdrm 2.4.16"
45 45
46 7) Push the commit and tag by saying 46 6) Push the commit and tag by saying
47 47
48 git push --tags origin master 48 git push --tags origin master
49 49
50 assuming the remote for the upstream libdrm repo is called origin. 50 assuming the remote for the upstream libdrm repo is called origin.
51 51
52 6) Use the release.sh script from the xorg/util/modular repo to 52 7) Use the release.sh script from the xorg/util/modular repo to
53 upload the tarballs to the freedesktop.org download area and 53 upload the tarballs to the freedesktop.org download area and
54 create an annouce email template. The script takes one argument: 54 create an annouce email template. The script takes one argument:
55 the path to the libdrm checkout. So, if a checkout of modular is 55 the path to the libdrm checkout. So, if a checkout of modular is