Re: [PATCH libdrm] RELEASING: update instructions to use meson instead of autotools

From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Engestrom <eric.engestrom@intel.com>
Cc: dri-devel@lists.freedesktop.org, Dylan Baker <dylan@pnwbakers.com>
Subject: Re: [PATCH libdrm] RELEASING: update instructions to use meson instead of autotools
Date: Mon, 18 Feb 2019 21:36:30 +0100	[thread overview]
Message-ID: <20190218203630.GT2665@phenom.ffwll.local> (raw)
In-Reply-To: <20190218174238.2qzj7o5cbpl4aezf@intel.com>

On Mon, Feb 18, 2019 at 05:42:38PM +0000, Eric Engestrom wrote:
> On Thursday, 2018-12-20 11:53:11 -0800, Dylan Baker wrote:
> > Quoting Eric Engestrom (2018-12-19 08:23:40)
> > > Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
> > > ---
> > >  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:
> 
> Just noticed I forgot to decrement item 4 & 5 :]
> 
> > >  
> > > -- 
> > > Cheers,
> > >   Eric
> > > 
> > 
> > Acked-by: Dylan Baker <dylan@pnwbakers.com>
> > 
> > But you should probably get someone other than just me to look at this.
> 
> There is no "libdrm maintainer", which makes everyone a libdrm
> maintainer :]
> 
> If nobody object, I'll push this in a few weeks (there's really no rush,
> but I want to make that move at some point, we have no reason to stay
> dependant on autotools now that we have better tools).

I double-checked that ninja dist does run the tests, so lgtm (with the
numbering adjusted):

Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel