View source for Fedora 13 QA Retrospective

== 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 13.  The feedback will be used as a basis for identifying areas for improvement for Fedora 14 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 [https://admin.fedoraproject.org/mailman/listinfo/test test@lists.fedoraproject.org].

== Providing feedback ==

Adding feedback is fairly straight forward.  If you already have a [https://admin.fedoraproject.org/accounts Fedora account] ...
# Login to the wiki
# Select ''[Edit]'' for the appropriate section below.
# Add your feedback using the format: <pre>* ~~~ - I like ____ about the new ____ process</pre>
# When done, ''Submit'' your changes

Otherwise, if you do not have a [https://admin.fedoraproject.org/accounts Fedora account], follow the instructions below ...
# Select the appropriate page for your feedback...
#* [http://fedoraproject.org/w/index.php?title=Test_Results:Fedora_13_QA_Retrospective/good&action=edit Something that worked well]
#* [http://fedoraproject.org/w/index.php?title=Test_Results:Fedora_13_QA_Retrospective/bad&action=edit Something that didn't work well]
#* [http://fedoraproject.org/w/index.php?title=Test_Results:Fedora_13_QA_Retrospective/wishlist&action=edit Anything on your QA wishlist]
# Add your feedback using the format: <pre>* ~~~ - I like ____ about the new ____ process</pre>
# When done, ''Submit'' your changes

== Feedback ==

=== Things that went well ===

{{Test_Results:Fedora_13_QA_Retrospective/good}}

* [[User:Jlaska|jlaska]] - ''Release Criteria'' - Having release criteria that have been reviewed and accepted by key stake holders really expedites testing by improving bug escalation time and uncertainty regarding user impact.  Instead of spending precious time debating the merits of each bug report, we can collectively debate the criteria ... and adjust as needed.
* [[User:Rhe|rhe]] - ''Trac Ticket for creating milestones'' - efficiently track the status of isos.
* [[User:Rhe|rhe]] - ''key of test results'' - more people can easily provide test results in one test case.

=== Could have been better ===

{{Test_Results:Fedora_13_QA_Retrospective/bad}}
* [[User:Jlaska|jlaska]] - ''freeze date between TC and RC'' - Because the alpha development freeze takes places ''after'' the test compose, the first alpha release candidate had a '''lot''' of change and was dead on arrival (see [http://lists.fedoraproject.org/pipermail/test/2010-February/088668.html thread discussing changes]).
* [[User:Jlaska|jlaska]] - ''live images'' - Not having daily Live images available for test left several Live installer bugs lurking until late.
* [[User:Rhe|rhe]] - ''use of real event urls'' - Redirect link urls can be used in emails, irc topic etc instead of real event urls.
* [[User:Jlaska|jlaska]] - ''firstboot modules'' - We don't have a way to know what firstboot modules are expected, we need to document this as release criteria, or write a test to report the issue (for details, see {{bz|574596}}).
* [[User:jlaska|jlaska]] - ''test days'' - [[Test_Day:2010-03-25_Printing|Printing]] test day did not have as many participants as we anticipated and hoped.  How come?
* [[User:Rhe|rhe]] - some candidates were not as expected to be available on time. Trac tickets were created by releng every time before the events. Is there anything else to do to make sure it's uploaded as scheduled next time?

=== Wishlist ===

{{Test_Results:Fedora_13_QA_Retrospective/wishlist}}

== References ==

* See [[Fedora_12_QA_Retrospective]]
* See [[Fedora_11_Retrospective_Notes]]
<references/>