[Test-Announce] Fedora 20 QA Retrospective page is up

The Retrospective page for Fedora 20 QA is now up (a bit late, but not as late as last time...): https://fedoraproject.org/wiki/Fedora_20_QA_Retrospective We use the retrospective page to track things that went well and things that didn't go so well during the Fedora 20 validation process, and for tracking ideas we have but don't have time to act on during the rush of doing validation (that's the wishlist). Please, add any feedback you have of this type to the retrospective page! There are instructions on the page for adding feedback. All feedback is useful, and once 20 validation is done, we'll take a look at all the items on the page and come up with specific recommendations for addressing them which we'll file as trac tickets and work on in the time before Fedora 21 validation starts up. We've been doing this for a while now and it's turned out to be a great way to keep constantly improving our processes. You can look at the previous pages for inspiration: https://fedoraproject.org/wiki/Category:QA_Retrospective And I'll copy/paste James' old list of leading questions to prompt feedback (thanks, James!): 1. Were you able to participate in any Fedora 20 Alpha, Beta or Final test runs? 2. What worked well, what prevented you from participating, were instructions clear? 3. What worked (or didn't work) well about Fedora Test Days this release? 4. Are you a maintainer, why do you think your critpath updates haven't been tested? What could you do to encourage more testing of your proposed updates? 5. Did you escalate any bugs for consideration as {Alpha,Beta,Final} release Blockers? Why not? Was the process well documented and did it make sense? 6. Did you attend or contribute to any Fedora blocker meetings? Why not? What did you like, dislike? What prevented you from participating? 7. Did you find any of the release criteria changes or validation test extensions particularly useful or problematic? 8. Can you think of any obviously important areas we are not currently covering in the validation tests and criteria? 9. How are you finding the new tools that have been introduced over the last few cycles, like the blocker bugs tool and the test day results tool? 10. Unlimited time and resource ... what do you think the the QA team should focus on for Fedora 21 and beyond </pony> -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net