Mac release criteria and testing

Yesterday the release team agreed to slip the F25 release by a week due to not being able to fulfill all the release criteria, namely: https://bugzilla.redhat.com/show_bug.cgi?id=1393846 This bug is one of the criteria that I assume the Workstation group values, because it helps us bring a working Fedora to people with Mac hardware. Several Workstation WG members were in the meeting and agreed this was an important criterion. The bug was found late because there is a lack of people/time/hardware for testing Mac-related criteria. One of the QA folks happened to run the test late and it turned out there was a small possibility our release could literally break someone's existing OS X/macOS install. We can argue about whether or not it was OK to block the release based on this bug. But more importantly this bug illustrates that Fedora success relies on shared responsibility. Creating release criteria has helped us create increasingly strong releases over the last several years. This process has been valiantly led by the QA team with much success. However, we can't simply add to criteria and then expect QA to simply "test all the things." It's incumbent on the WGs to pitch in where it makes sense to ensure success. I've taken some steps to help personally with some of this testing since I have some Mac hardware. And I'm looking to other Workstation WG members and people with affinity for the desktop to do the same during the F26 release cycle. If we can't bring together that kind of effort, we should drop the relevant Mac-related criteria (or call them best-effort or non-blocking). -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com