From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Radke <a.radke@arcor.de>
Subject: Re: [ANNOUNCE] xf86-video-intel 2.99.917
Date: Tue, 26 Jan 2016 19:03:35 +0100
Message-ID: <20160126190335.198db4f5@laptop64.home>
References: <20141221144758.GA10527@nuc-i3427.alporthouse.com>
 <20150506200257.GR16466@betterave.cristau.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1186123424=="
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
In-Reply-To: <20150506200257.GR16466@betterave.cristau.org>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: Julien Cristau <jcristau@debian.org>
Cc: intel-gfx@lists.freedesktop.org, xorg@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

--===============1186123424==
Content-Type: multipart/signed; micalg=pgp-sha1;
 boundary="Sig_/7J_wzIEEuG2zfUe=AYfMD+h"; protocol="application/pgp-signature"

--Sig_/7J_wzIEEuG2zfUe=AYfMD+h
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

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:
>=20
> > Snapshot 2.99.917 (2014-12-21)
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> > 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.=20
> How imminent is imminent?  This driver hasn't had a proper release in
> over a year and a half, this is getting ridiculous...
>=20
> 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

--Sig_/7J_wzIEEuG2zfUe=AYfMD+h
Content-Type: application/pgp-signature
Content-Description: Digitale Signatur von OpenPGP

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlantPcACgkQLju01StYJ8hpQgCeItpKmnf6jELdkcY3XHZdMPD1
OcgAnAnBb0eoZ2y5GoO/xkv44PGwsVdJ
=mGst
-----END PGP SIGNATURE-----

--Sig_/7J_wzIEEuG2zfUe=AYfMD+h--

--===============1186123424==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSW50ZWwtZ2Z4
IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnRlbC1nZngK

--===============1186123424==--