Fedora 17 QA Retrospective

From FedoraProject

Revision as of 17:32, 23 May 2012 by Bruno (Talk | contribs)

Jump to: navigation, search

Contents

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

  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

Test Results:Fedora 17 QA Retrospective/good

  • Adamwill - Pushing back the TC dates continued to help a lot with getting validation done on time
  • Bruno - The gcc 4.7 rebuild got done early enough, that we didn't have blocker issues caused by it

Could have been better

Test Results:Fedora 17 QA Retrospective/bad

  • Adamwill - noloader landing between Beta TC1 and Beta TC2 was way too late and caused extensive havoc
  • Adamwill - maybe just because we have longer for TCs now, but RC period feels very short: RC1 date is a Thursday, Go/No-Go is the following Wednesday, that's 6 days but only 4 business days of validate / fix / respin
  • Adamwill - the ability to add stuff to comps during freezes finally bit us on the ass, as I knew it eventually would: Bugzilla: #807879. Adding gnome-boxes to comps during Beta freeze broke networking in KVMs
  • Adamwill - desktop team was sad that we couldn't co-ordinate Beta release with the GNOME 3.4 final release so 3.4 final made Beta
  • Adamwill - pulling livecd-tools 17.7 as NTH for RC4 to 'fix' https://bugzilla.redhat.com/show_bug.cgi?id=810104 turned out to be the wrong call, it didn't fix that and it broke https://bugzilla.redhat.com/show_bug.cgi?id=811412
  • Adamwill - we definitely need to revisit the schedule; we need to find out exactly what has to happen between a 'go' call and the release, figure out how long that actually takes, and move the go/no-go and release readiness meetings to account for it. the day of dead time between go/no-go and release readiness is a complete waste of time
  • Kparal - Blocker bug meetings should not be on Friday. We lose a lot of Europe guys presence this way, because it's Friday evening for them (me included). 17.00 UTC is fine, but it must not be the Friday.

Wishlist

Test Results:Fedora 17 QA Retrospective/wishlist

  • tflink - it would be nice to have a better system for tracking current blockers. While the current wiki-based system is great, it's only updated once per hour and we don't always notice right away when the wiki updates start failing.
  • Bruno - I think it would be useful to review the blocker bugs to see if we can spot any trends. Just looking at the component counts might be useful. even if we don't do anything more.
  • Bruno - It seemed like install / upgrade testing wasn't getting done early early enough. People (like me) running the branched release don't see these issues in routine use. We may want to find some way to encourage or automate testing on installs and upgrades in order to get earlier warning of problems.
  • Bruno - The F17 branch of the spin-kickstarts repo kept getting changed during freezes. It would be nice to have a way to stage this during freezes so that the spin-kickstarts package included on the install disk matches what we use for building. This is important for GPL compliance.

Recommendations

After enough time has been given for feedback, the QA team will discuss and make recommendations on changes to prioritize for Fedora 18. 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 18 roadmap in the QA TRAC instance.

References