Signed-off-by: Eric Engestrom <eric.engestrom@xxxxxxxxx> --- RELEASING | 27 ++++++++------------------- 1 file changed, 8 insertions(+), 19 deletions(-) diff --git a/RELEASING b/RELEASING index 7e03e3b9acb1cbfb261a..d1ad8e3b4ad16d4ca14f 100644 --- a/RELEASING +++ b/RELEASING @@ -9,25 +9,14 @@ 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. - - 2) Run autoconf and then re-run ./configure so the build system - picks up the new version number. - - 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. + 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 `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. 4) Push the updated master branch with the bumped version number: -- Cheers, Eric _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
