summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarek Olšák <marek.olsak@amd.com>2018-02-17 20:25:02 +0100
committerMarek Olšák <marek.olsak@amd.com>2018-02-17 20:25:02 +0100
commite87a87925ea23e84ed6f67de73a5ef2713ca2c49 (patch)
tree863e178cc25f334a5c35db14a33be5b22c747040
parenta05f5ac3023fd9a16b0dfffe30786e83c7513197 (diff)
RELEASING: mention meson
-rw-r--r--RELEASING6
1 files changed, 3 insertions, 3 deletions
diff --git a/RELEASING b/RELEASING
index 262ca08d..7e03e3b9 100644
--- a/RELEASING
+++ b/RELEASING
@@ -9,9 +9,9 @@ However, this is up to whoever is driving the feature in question.
Follow these steps to release a new version of libdrm:
- 1) Bump the version number in configure.ac. We seem to have settled
- for 2.4.x as the versioning scheme for libdrm, so just bump the
- micro version.
+ 1) Bump the version number in configure.ac and meson.build. We seem
+ to have settled for 2.4.x as the versioning scheme for libdrm, so
+ just bump the micro version.
2) Run autoconf and then re-run ./configure so the build system
picks up the new version number.