geemili
/
drm
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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>
main
Eric Engestrom 2018-12-19 12:16:25 +00:00 committed by Eric Engestrom
parent dddeff5028
commit e4f090f3c2
1 changed files with 9 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
RELEASING
View File

@ -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: Follow these steps to release a new version of libdrm:
1) Bump the version number in configure.ac and meson.build. We seem 1) Bump the version number in meson.build. We seem to have settled for
to have settled for 2.4.x as the versioning scheme for libdrm, so 2.4.x as the versioning scheme for libdrm, so just bump the micro
just bump the micro version. version.
2) Run autoconf and then re-run ./configure so the build system 2) Run `ninja -C builddir/ dist` to generate the tarballs.
picks up the new version number. 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 3) Push the updated master branch with the bumped version number:
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:
git push origin master git push origin master
assuming the remote for the upstream libdrm repo is called origin. 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 upload the tarballs to the freedesktop.org download area and
create an announce email template. The script takes one argument: create an announce email template. The script takes one argument:
the path to the libdrm checkout. So, if a checkout of modular is the path to the libdrm checkout. So, if a checkout of modular is