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

[Adam Williamson]

So, the last of these emails I sent was eight years ago, time flies,
huh? :)

Sudhir suggested bringing these back, and it seemed like a fine idea,
so I did! I've created a Fedora 35 Retrospective page:


https://fedoraproject.org/wiki/Fedora_35_QA_Retrospective

In the past we would've created this page *during* Fedora 35
validation, so we could note things as we went along. I'll try and
remember to create one for Fedora 36 in a month or two.

Just in case anyone wasn't around in 2013 :P, here's how it works!

We use the retrospective page to track things that went well and things
that didn't go so well during the Fedora 35 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 after the page has been up for a while, 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 issues and
work on in the time before Fedora 36 validation starts up.

You can look at the previous pages for inspiration:

https://fedoraproject.org/wiki/Category:QA_Retrospective

And once again I'll copy/paste James Laska's old list of leading questions
to prompt feedback, because it's still pretty good:

     1. Were you able to participate in any Fedora 35 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
        {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 tools that we use for the process, 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 36 and beyond </pony>

-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

_______________________________________________
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure