[Mesa-dev] [RFC] Mesa 17.3.x release problems and process improvements
Eric Anholt
eric at anholt.net
Tue Mar 13 19:59:55 UTC 2018
Kenneth Graunke <kenneth at whitecape.org> writes:
> [ Unknown signature status ]
> On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote:
> [snip]
>> I've been doing this for Intel. Developers are on the hook to fix their
>> bugs, but you can't make them do it. They have many pressures on them,
>> and a maintainer can't make the call as to whether a rendering bug is
>> more important than day-1 vulkan conformance, for example.
>>
>> We could heighten the transparency of what is blocking the build by
>> publicizing the authors of bisected blocking bugs to Phoronix, which
>> might get things moving.
>
> I hope you're being sarcastic here, or else I'm misunderstanding your
> proposal. Public shaming of developers who create bugs has absolutely
> no place in the Mesa community, IMHO. It would foster the kind of toxic
> community that none of us want to be a part of.
Agreed!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180313/d826fc16/attachment.sig>
More information about the mesa-dev
mailing list