#135: Fedora 23 Retrospective
---------------------+---------------------
Reporter: jzb | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords: meeting |
---------------------+---------------------
Comment (by pbrobinson):
The QA process was clearly something that went terribly wrong (again) and
needs a large rethink and to be better aligned with the Fedora QA general
process.
A few big ones:
* updates in testing not getting appropriate karma (docker at least)
* apparent critical release criteria having proper test cases and actually
in the matrix to ensure verification eg ansible [1] and root bind
mount[2].
We should never get to a case we're in the 11th hour and 59th minute of a
release and discover an apparent core feature [3] is terribly broken.
To be clear this isn't directed at any one person, but the whole cloud WG.
It really wasn't good enough. If it can't be tested by automation then it
should be tested manually, either way the results from any automation
should be closely checked and verified.
[1] https://fedorahosted.org/cloud/ticket/126
[2]
https://lists.fedoraproject.org/pipermail/cloud/2015-October/006033.html
[3]
https://lists.fedoraproject.org/pipermail/cloud/2015-October/006015.html
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/135#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
