On 07/11/2013 11:22 AM, Peter Jones wrote:
The point of this isn't just that it was broken, though - the concern here is that the test suite said it was not working. What else isn't working because nobody has even looked? What's worrisome here is not merely that a major security feature wasn't working. While that is troubling, the fact of the matter is that people *not* on your team thought it wasn't working, and assumed that you knew. The test suite is giving failing results. That's not usually an indicator of high quality or success.
Yes, this is a serious issue for any architecture. It's more of a people problem than technical though. We can solve it for gcc on ARM specifically, but as a general case I don't have an easy answer.
The worry isn't that there's one thing here or there that doesn't work - the worry is that there are relatively major Fedora features that we've advertised in big letters in the relatively recent past that simply don't work because nobody has paid any attention to whether or not they work.
Hmm. -- Brendan Conoboy / Red Hat, Inc. / blc@xxxxxxxxxx -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
