Added by Paul Cutler, last edited by Alexandre Franke on May 30, 2010  (view change) show comment

Labels:

bugs bugs Delete
tasks tasks Delete
issues issues Delete
fits fits Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

The Foresight Quality Assurance and Bug team is dedicated to helping Foresight Linux run without issues for its users.

Foresight Quality Assurance Team Members

  • Paul Cutler (pcutler) (Team Lead)
  • Kevin Harriss (specialkevin)
  • Ken VanDine (kenvandine)
  • Antonio Meireles (doniphon)
  • Paul Scott-Wilson (pscott)
  • Eric Lake (etank)
  • Erosion (Erosion)
  • Rune Morling (ermo)
  • Lance Haig (LanceHaig)
  • Jayson Rowe (jayson_r)
  • Tomas Forsman (TForsman)

Interested in helping out test packages or bug triaging?  Read the following HowTo's and add your name to the team member list above!

Last Bug Hunt Week was:  Wednesday, October 10th - Tuesday, October 16th.

Next Bug Hunt Week

  • Next Bug Hunt Week is:

Please stop by #foresight-qa on Freenode IRC and lend a hand

Package Contest Sprint

There has been talk about doing a sprint to wrap up the QA-testing of the remaining completed packages

When you have tested an issue, please use the 'Back to QA' option in the menu on the left under the heading 'Available Workflow Actions' (if it is available) and leave a comment that you have tested the package in question.

The QA workflow hasn't been completely formalized as of yet; however, you can ping pcutler on IRC and he will supply you with access to the shared -QA issues spreadsheet. I (ermo) also keep mine in a tomboy note and update the spreadsheet every 5 issues or so.

NB Keep in mind that packages need QA on both x86_64 AND x86

Issues / Bug Management

Join the Foresight QA team, and report bugs and issues with Foresight, triage and verify issues filed in the bug tracker, or help package software containing bug fixes.

Package testing

  • When testing packages, running the QA branch full time is recommended, because:
    • 2-qa helps test what our users will be using soon.
    • 2-qa should be more stable than 2-devel.
    • The Foresight developers try to keep the delta between the fl:2-devel label and the fl:2-qa label small.
  • Please see HOWTO switch to the QA version of Foresight 2.x

TODO - Promoting packages from 2:Dev to 2:QA to FL:2 HowTo