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 35. The feedback will be used as a basis for identifying areas for improvement for Fedora 36 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
- Gwjasu - I like ____ about the new ____ process
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
adamwill - We slipped both Beta and Final appropriately and did not rush the releases. adamwill - The final RC was built plenty of time before Go/No-Go, allowing for a good amount of testing. adamwill - We were able to resolve all the KDE-related blockers with good co-operation from Fedora and upstream KDE folks, especially Aleix Pol who resolved a lot of the Discover blockers.
Could have been better
adamwill - It took a long time to work through all the iterations of the fedora-third-party/SELinux bug. Seems like we could have tightened the loop on that somehow. adamwill - Movement on the KDE blockers was initially slow, if we could have resolved them earlier we would have had more time to find and fix the bugs that eventually delayed Final.
Wishlist
Recommendations
After enough time has been given for feedback, the QA team will discuss and make recommendations on changes to prioritize for Fedora 36. 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 QA issue tracker.