From: Daniel Vetter <daniel@ffwll.ch>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Kristian Høgsberg" <hoegsberg@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [ANNOUNCE] libdrm 2.4.94
Date: Fri, 31 Aug 2018 10:22:22 +0200 [thread overview]
Message-ID: <20180831082222.GN21634@phenom.ffwll.local> (raw)
In-Reply-To: <d95b33ae-e68a-0282-df3e-06d86762a99c@daenzer.net>
On Fri, Aug 24, 2018 at 06:37:35PM +0200, Michel Dänzer wrote:
> On 2018-08-24 6:27 p.m., Kristian Høgsberg wrote:
> >
> > I don't know what all is pending for libdrm, but I know that we've
> > agreed on a very low bar for when to release libdrm:
> >
> > "The release criteria for libdrm is essentially "if you need a release,
> > make one". There is no designated release engineer or maintainer.
> > Anybody is free to make a release if there's a certain feature or bug
> > fix they need in a released version of libdrm."
>
> First of all, let me assure you that I'm not picking on you in
> particular, this applies to anybody who makes a release.
>
> Quite frankly, that sucks. :) A brief "heads up, I'm cutting a libdrm
> release, let me know if there's something you want in it" e-mail at
> least 24 hours (not counting weekend days) before making the release
> shouldn't be asking too much.
Given that making a libdrm release is pretty much for free I'm not sure
about the concern. We've had plenty of back-to-back libdrm releases. Since
libdrm is supposed to be always in release state (it's mostly just headers
and simple wrappers) I don't see a downside aside from "looks mildly
silly" :-)
If we'd have a libdrm release maintainer that'd be different, but no one
volunteered (and for years) so that's unlikely to change.
-Daniel
--
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
next prev parent reply other threads:[~2018-08-31 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 22:37 [ANNOUNCE] libdrm 2.4.94 Kristian H. Kristensen
2018-08-24 5:43 ` Laurent Carlier
2018-08-24 16:19 ` Kristian Høgsberg
2018-08-24 8:13 ` Michel Dänzer
2018-08-24 16:27 ` Kristian Høgsberg
2018-08-24 16:37 ` Michel Dänzer
2018-08-31 8:22 ` Daniel Vetter [this message]
2018-08-24 17:44 ` Laurent Carlier
2018-08-27 9:38 ` Michel Dänzer
2018-08-27 10:03 ` Emil Velikov
2018-08-27 10:06 ` Michel Dänzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180831082222.GN21634@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@gmail.com \
--cc=michel@daenzer.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.