drm: Branch 'master'

 RELEASING |   29 +++++++++--------------------
 1 file changed, 9 insertions(+), 20 deletions(-)

New commits:
commit e4f090f3c23d7b92068ee182a277700ba3988c36
Author: Eric Engestrom <[email protected]>
Date:   Wed Dec 19 12:16:25 2018 +0000

    RELEASING: update instructions to use meson instead of autotools
    
    Signed-off-by: Eric Engestrom <[email protected]>
    Acked-by: Dylan Baker <[email protected]>
    Acked-by: Daniel Vetter <[email protected]>

diff --git a/RELEASING b/RELEASING
index 7e03e3b9..903c1761 100644
--- a/RELEASING
+++ b/RELEASING
@@ -9,33 +9,22 @@ 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 and meson.build. 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 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.
+  2) Run `ninja -C builddir/ dist` to generate the tarballs.
+     Make sure that the version number of the tarball name in
+     builddir/meson-dist/ matches the number you bumped to. Move that
+     tarball to the libdrm repo root for the release script to pick up.
 
-  3) Verify that the code passes "make distcheck".  Running "make
-     distcheck" should result in no warnings or errors and end with a
-     message of the form:
-
-	=============================================
-	libdrm-X.Y.Z archives ready for distribution:
-	libdrm-X.Y.Z.tar.gz
-	libdrm-X.Y.Z.tar.bz2
-	=============================================
-
-     Make sure that the version number reported by distcheck and in
-     the tarball names matches the number you bumped to in configure.ac.
-
-  4) Push the updated master branch with the bumped version number:
+  3) Push the updated master branch with the bumped version number:
 
 	git push origin master
 
      assuming the remote for the upstream libdrm repo is called origin.
 
-  5) Use the release.sh script from the xorg/util/modular repo to
+  4) Use the release.sh script from the xorg/util/modular repo to
      upload the tarballs to the freedesktop.org download area and
      create an announce email template.  The script takes one argument:
      the path to the libdrm checkout. So, if a checkout of modular is


--