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 12. The feedback will be used as a basis for identifying areas for improvement for Fedora 13 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 fedora-test-list@redhat.com.
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
Otherwise, if you do not have a Fedora account, follow the instructions below ...
- 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
- jlaska - Having QA/SOP_Test_Day_management was invaluable and resulted in a consistent look'n'feel for Fedora 12 test days
- jlaska - The creation of the test-announce@lists.fedorahosted.org mailing list made it much easier to announce test events. With a single mailing list for announcements, it's harder to miss any events.
- jlaska - Consistent announcement of ISO test events from Liam was great to ensure a consistent testing experience (see User:Liam/Draft_Install_Test_SOP).
- jlaska - We had more ISO install test runs, and they were earlier in each milestone
- jlaska - F-12 ISO Install testing solicited more testing from outside the core install test group. 27 different people contributed test feedback on the wiki test matrix during F-12. . 19 different people contributed test feedback on the wiki test matrix during F-11.
- jlaska - Automated test cases provided for the Power Management test day == awesome!
- Viking-Ice - Increase in SIG and maintainers for hosting and holding their own test days and specific application testing.
- Viking-Ice - Nightly-composes of rawhide test images.
- Viking-Ice - Improvement in advertisement testing/test day's
- Viking-Ice - Increase in request from sig/maintainers in Fedora QA Trac system.
- Viking-Ice - Increase in how to debug <component> for reporters to follow and provide better bug report.
- Viking-Ice - Consistency in how to debug <component> pages for better look and feel.
- Viking-Ice - Automatic bug reporting tool develop to help provide better bug reporting and allow technical challenge people to participate report and provide feedback.
- Viking-Ice - Better collaboration and participation from developers/maintainers with QA.
Could have been better
- anonymous
uname -a hera.localdomain 2.6.31.12-174.2.3.fc12.x86_64 #1 SMP Mon Jan 18 19:52:07 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux language brazilian portuguese
this works for me ls -l *.rpm
look at "./" preceding the char "*" this works for me ls -l ./*.pps
but
this does not works for me
ls -l *.pps ls: invalid option -- 'P' Experimente "ls --help" para mais informações.
I think this is a bug
- jlaska - it may be, but I believe you might want to confirm what the asterix is expanding to in the directory you are running the command
ls -l *.pps. It's possible it is expanding to a filename that has -P as the first 2 characters, which confuses the ls command. What doesecho *.ppsyield? You may wish to enclose the command in quotes,ls -l "*.pps". If problems remain, please raise the issue on the users or test list. - jlaska - The blocker bug meetings during the Final milestone were too long.
- Kparal - The preupgrade could receive more testing/test cases
- Kparal - test-announce wasn't used for announcing RC candidates IIRC, we should make sure all important events are mentioned there
Wishlist
- 66.187.233.202 - I would like a pony
- jlaska - I also want a pony
- Kparal - I would like to see more people in beta/RC testing. New templates are going to solve the practical part (display multiple results easily), now the issue is to attract more people. I would like to visit get-fedora page and see there "Fedora 13 Release Candidate available! Download <<here>>, help with testing <<here>>". And links to our wiki pages describing how to contribute on testing. I think Ubuntu is doing similar thing (large banners "Beta available" on their front page). That could bring a lot of new people.
Recommendations
After enough feedback has been collected, the QA team will discuss and make recommendations on changes for Fedora 13. This section will be filled in at that time.