diff options
| author | Eric Engestrom <eric.engestrom@intel.com> | 2018-12-19 12:16:25 +0000 |
|---|---|---|
| committer | Eric Engestrom <eric@engestrom.ch> | 2019-10-14 15:57:26 +0000 |
| commit | e4f090f3c23d7b92068ee182a277700ba3988c36 (patch) | |
| tree | 9f7873609bf7a43615982a41acd9da09e942a869 | |
| parent | dddeff5028e1f3f34f67846c12876cd189c61bd1 (diff) | |
| download | libdrm-e4f090f3c23d7b92068ee182a277700ba3988c36.tar.gz libdrm-e4f090f3c23d7b92068ee182a277700ba3988c36.tar.bz2 libdrm-e4f090f3c23d7b92068ee182a277700ba3988c36.zip | |
RELEASING: update instructions to use meson instead of autotools
Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
Acked-by: Dylan Baker <dylan@pnwbakers.com>
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
| -rw-r--r-- | RELEASING | 29 |
1 files changed, 9 insertions, 20 deletions
@@ -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 |