aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEric Anholt2016-07-20 14:24:00 -0500
committerEric Anholt2016-07-24 20:36:34 -0500
commitf19cd3a52827a2368040649c2fc5e7e75db10d08 (patch)
treef36d605e381df54b9ecc972591ce1499ea1214da /RELEASING
parent0caa84cb046156b9b2ca248d32af9548b04316e1 (diff)
downloadexternal-libgbm-f19cd3a52827a2368040649c2fc5e7e75db10d08.tar.gz
external-libgbm-f19cd3a52827a2368040649c2fc5e7e75db10d08.tar.xz
external-libgbm-f19cd3a52827a2368040649c2fc5e7e75db10d08.zip
Simplify the RELEASING steps based on current release.sh.
Since release.sh creates and pushes a libdrm-$VERSION tag for us, there's no need to also have the user manually generating a $VERSION tag as well. I also dropped the "optional" part of distcheck. You shouldn't have pushed master with a version bump that hasn't passed distcheck. Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING26
1 files changed, 6 insertions, 20 deletions
diff --git a/RELEASING b/RELEASING
index 62c5be9f..262ca08d 100644
--- a/RELEASING
+++ b/RELEASING
@@ -9,21 +9,14 @@ However, this is up to whoever is driving the feature in question.
9 9
10Follow these steps to release a new version of libdrm: 10Follow these steps to release a new version of libdrm:
11 11
12 1) Ensure that there are no local, uncommitted/unpushed 12 1) Bump the version number in configure.ac. We seem to have settled
13 modifications. You're probably in a good state if both "git diff
14 HEAD" and "git log master..origin/master" give no output.
15
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 13 for 2.4.x as the versioning scheme for libdrm, so just bump the
18 micro version. 14 micro version.
19 15
20 3) Run autoconf and then re-run ./configure so the build system 16 2) Run autoconf and then re-run ./configure so the build system
21 picks up the new version number. 17 picks up the new version number.
22 18
23 4) (optional step, release.sh will make distcheck for you, but it can be 19 3) Verify that the code passes "make distcheck". Running "make
24 heart warming to verify that make distcheck passes)
25
26 Verify that the code passes "make distcheck". Running "make
27 distcheck" should result in no warnings or errors and end with a 20 distcheck" should result in no warnings or errors and end with a
28 message of the form: 21 message of the form:
29 22
@@ -36,20 +29,13 @@ Follow these steps to release a new version of libdrm:
36 Make sure that the version number reported by distcheck and in 29 Make sure that the version number reported by distcheck and in
37 the tarball names matches the number you bumped to in configure.ac. 30 the tarball names matches the number you bumped to in configure.ac.
38 31
39 5) Commit the configure.ac change and make an annotated tag for that 32 4) Push the updated master branch with the bumped version number:
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
42 the command is:
43
44 git tag -a 2.4.16 -m "libdrm 2.4.16"
45
46 6) Push the commit and tag by saying
47 33
48 git push --tags origin master 34 git push origin master
49 35
50 assuming the remote for the upstream libdrm repo is called origin. 36 assuming the remote for the upstream libdrm repo is called origin.
51 37
52 7) Use the release.sh script from the xorg/util/modular repo to 38 5) Use the release.sh script from the xorg/util/modular repo to
53 upload the tarballs to the freedesktop.org download area and 39 upload the tarballs to the freedesktop.org download area and
54 create an announce email template. The script takes one argument: 40 create an announce email template. The script takes one argument:
55 the path to the libdrm checkout. So, if a checkout of modular is 41 the path to the libdrm checkout. So, if a checkout of modular is