[patch] Make r600 non-experimental

[Alex Deucher]

On Wed, May 22, 2013 at 2:07 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Wed, May 22, 2013 at 4:58 AM, Rafael Espíndola
> <rafael.espindola at gmail.com> wrote:
>>
>> On 22 May 2013 00:19, David Blaikie <dblaikie at gmail.com> wrote:
>> > If this means we'll release R600 in 3.4, do we have adequate test
>> > coverage/buildbots?
>>
>> We are getting it. It has a much better track record of including
>> tests with bug fixes these days. We can also still call it
>> experimental for release purposes, but having it build by default
>> seemed a net win.
>
>
> Do we have a procedure for that? (do we release with targets in
> "experimental" states? I guess we might've - it presumably includes some
> release docs, do we have those? ("hey, this release has an R600 backend, but
> it's experimental, <caveat caveat caveat>")) or any way to track that we
> need to pull it out of the release?

FWIW, we are actively using it as the shader compiler for our open
source OpenGL and OpenCL drivers which will be shipping with most
Linux distros.

Alex