From Fedora Project Wiki

(Created page with "== 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 testin...")
 
 
(4 intermediate revisions by 2 users not shown)
Line 6: Line 6:
  
 
== Providing feedback ==
 
== Providing feedback ==
* [[User:Gwjasu|Gwjasu]] - I like ____ about the new ____ process
+
 
 
Adding feedback is fairly straight forward.  If you already have a [https://admin.fedoraproject.org/accounts Fedora account] ...
 
Adding feedback is fairly straight forward.  If you already have a [https://admin.fedoraproject.org/accounts Fedora account] ...
 
# Login to the wiki
 
# Login to the wiki
Line 27: Line 27:
  
 
=== Things that went well ===
 
=== Things that went well ===
{{Test_Results:Fedora_24_QA_Retrospective/good}}
+
* 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 ===
 
=== Could have been better ===
{{Test_Results:Fedora_24_QA_Retrospective/bad}}
+
* 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 ===
 
=== Wishlist ===
{{Test_Results:Fedora_24_QA_Retrospective/wishlist}}
 
  
 
== Recommendations ==
 
== Recommendations ==
 
After enough time has been given for feedback, the [[QA]] team will discuss and make recommendations on changes to prioritize for Fedora 25.  This section organizes and lists the recommendations.
 
After enough time has been given for feedback, the [[QA]] team will discuss and make recommendations on changes to prioritize for Fedora 25.  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://fedorahosted.org/fedora-qa/milestone/Fedora%2022 Fedora 25 roadmap] in the [https://fedorahosted.org/fedora-qa QA TRAC instance].
+
In order to coordinate efforts, and measure effectiveness of recommendations, please record and track any action taken in the [https://fedorahosted.org/fedora-qa/milestone/Fedora%2025 Fedora 25 roadmap] in the [https://fedorahosted.org/fedora-qa QA TRAC instance].
  
 
== References ==
 
== References ==

Latest revision as of 04:02, 5 July 2016

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 24. The feedback will be used as a basis for identifying areas for improvement for Fedora 25 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 ...

  1. Login to the wiki
  2. Select [Edit] for the appropriate section below.
  3. Add your feedback using the format:
    * ~~~ - I like ____ about the new ____ process
  4. 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.

  1. Select the appropriate page for your feedback...
  2. Add your feedback using the format:
    * ~~~ - I like ____ about the new ____ process
  3. 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 25. 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 Fedora 25 roadmap in the QA TRAC instance.

References