public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andreas Radke <a.radke@arcor.de>
To: Julien Cristau <jcristau@debian.org>
Cc: intel-gfx@lists.freedesktop.org, xorg@lists.freedesktop.org
Subject: Re: [ANNOUNCE] xf86-video-intel 2.99.917
Date: Tue, 26 Jan 2016 19:03:35 +0100	[thread overview]
Message-ID: <20160126190335.198db4f5@laptop64.home> (raw)
In-Reply-To: <20150506200257.GR16466@betterave.cristau.org>


[-- Attachment #1.1: Type: text/plain, Size: 1187 bytes --]

Am Wed, 6 May 2015 22:02:57 +0200
schrieb Julien Cristau <jcristau@debian.org>:

> On Sun, Dec 21, 2014 at 14:47:58 +0000, Chris Wilson wrote:
> 
> > Snapshot 2.99.917 (2014-12-21)
> > ==============================
> > 3 months drifted by whilst I looked elsewhere for bugs.. The
> > highlight of bugs fixed here are a couple of workarounds required
> > for Broadwell and making sure that the rasterisation code is
> > symmetric under inversions. However, as a couple of crashers
> > slipped through into 2.99.916 (though not actual regressions in
> > 2.99.916 per se) and 3 months have passed, we should make one more
> > snapshot before an imminent release. 
> How imminent is imminent?  This driver hasn't had a proper release in
> over a year and a half, this is getting ridiculous...
> 
> Cheers,
> Julien

What happened to the "release early/release often" rule? It has pushed
OSS much faster forward than it now goes.

Distributions are forced to randomly pick some git snapshot. Often it's
not too much stuff broken. No stable release or branch we can rely on.

Is Intel not able to maintain its own device driver in a usable way?

Andy
Arch Linux

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-26 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 14:47 [ANNOUNCE] xf86-video-intel 2.99.917 Chris Wilson
2015-05-06 20:02 ` Julien Cristau
2016-01-26 18:03   ` Andreas Radke [this message]
2016-01-26 20:51     ` [Intel-gfx] " René Rebe
2016-07-19 17:49       ` Peter Hessler
  -- strict thread matches above, loose matches on Subject: below --
2016-01-28  8:06 Lampshade
     [not found] ` <widruunxaxmmvcqlyprq@clkp>
2016-02-01 16:33   ` Lampshade

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=20160126190335.198db4f5@laptop64.home \
    --to=a.radke@arcor.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jcristau@debian.org \
    --cc=xorg@lists.freedesktop.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox