Introduction
This page is intended to gather feedback from the Fedora QA community on things that worked well and things that could have been better with the testing of Fedora 27. The feedback will be used as a basis for identifying areas for improvement for Fedora 27 testing. Any thoughts, big or small, are valuable. If someone already provided feedback similar to what you'd like to add, don't worry ... add your thoughts regardless.
For any questions or concerns, send mail to test@lists.fedoraproject.org.
Providing feedback
Adding feedback is fairly straight forward. If you already have a Fedora account ...
- Login to the wiki
- Select [Edit] for the appropriate section below.
- Add your feedback using the format:
* ~~~ - I like ____ about the new ____ process
- When done, Submit your changes
Anonymous
If you do not have a Fedora account, follow the instructions below to submit anonymous feedback. Please note, mediawiki records the IP address associated with any anonymous page edits.
- Select the appropriate page for your feedback...
- Add your feedback using the format:
* ~~~ - I like ____ about the new ____ process
- When done, Submit your changes
Feedback
Things that went well
- I liked the gating of fedora-kickstarts using Pagure as it allowed us to control which kicktart file changes went to production while still allowing people to record non-critical changes to bring in after a freeze.
Could have been better
- Having random compose failures for some artifacts was annoying. It made testing spins harder and ended up with design spin not being part of the normal release.
Wishlist
Recommendations
After enough time has been given for feedback, the QA team will discuss and make recommendations on changes to prioritize for Fedora 28. This section organizes and lists the recommendations.
In order to coordinate efforts, and measure effectiveness of recommendations, please record and track any action taken in the [ https://pagure.io/fedora-qa Fedora 28 roadmap] in the QA Pagure instance.