From Fedora Project Wiki

< QA‎ | Meetings

fp-wiki>ImportUser
(Imported from MoinMoin)
 
(clean up and note logs were never posted)
 
(One intermediate revision by one other user not shown)
Line 3: Line 3:
== Agenda ==
== Agenda ==


1. Review actions from last week
# Review actions from last week
1. Review F7 plan - https://www.redhat.com/archives/fedora-advisory-board/2006-December/msg00170.html
# Review F7 plan - https://www.redhat.com/archives/fedora-advisory-board/2006-December/msg00170.html
i. Do we have a plan/tools/docs for testing each feature listed?
#: Do we have a plan/tools/docs for testing each feature listed?
i. Can we test all that stuff in the time given?
#: Can we test all that stuff in the time given?
i. Divide the features into categories/tiers, e.g.:
#: Divide the features into categories/tiers, e.g.:
i. '''Required''' - release will slip until it works
#: '''Required''' - release will slip until it works
i. '''Desired'''  - we want this to work but we may be forced to ship it with known bugs and fix them later
#: '''Desired'''  - we want this to work but we may be forced to ship it with known bugs and fix them later
i. '''Delicate''' - If this doesn't work by Feature Freeze (Test2), it can't go in at all
#: '''Delicate''' - If this doesn't work by Feature Freeze (Test2), it can't go in at all
i. Others?
#: Others?
1. Define general QA workflows - "walkthroughs" for things we test.
# Define general QA workflows - "walkthroughs" for things we test.
i. How do we test new packages in updates-testing?
#: How do we test new packages in updates-testing?
i. What about new stuff in rawhide?
#: What about new stuff in rawhide?
i. How do you do installer testing?
#: How do you do installer testing?
i. What do you do to test a new release (like Test1)?
#: What do you do to test a new release (like Test1)?
i. Get these things on the wiki or mailing list so we can discuss and improve them.
#: Get these things on the wiki or mailing list so we can discuss and improve them.
1. QA tool updates - fedora-updates-system (lmacken), RHTS (poelstra/dmalcolm), SNAKE (wwoods)
# QA tool updates - fedora-updates-system (lmacken), RHTS (poelstra/dmalcolm), SNAKE (wwoods)
i. fedora-updates-system (lmacken)
#: fedora-updates-system (lmacken)
i. RHTS (poelstra/dmalcolm)
#: RHTS (poelstra/dmalcolm)
i. SNAKE (wwoods)
#: SNAKE (wwoods)
1. Anything else
# Anything else


== Notes ==
== Notes ==


A log and meeting notes should be posted after the meeting, if someone can log it.
log and notes never posted (2015-01-05).

Latest revision as of 00:14, 6 January 2015

Fedora QA Meeting - December 21 2006, 0100 UTC, #fedora-testing on freenode

Agenda

  1. Review actions from last week
  2. Review F7 plan - https://www.redhat.com/archives/fedora-advisory-board/2006-December/msg00170.html
    Do we have a plan/tools/docs for testing each feature listed?
    Can we test all that stuff in the time given?
    Divide the features into categories/tiers, e.g.:
    Required - release will slip until it works
    Desired - we want this to work but we may be forced to ship it with known bugs and fix them later
    Delicate - If this doesn't work by Feature Freeze (Test2), it can't go in at all
    Others?
  3. Define general QA workflows - "walkthroughs" for things we test.
    How do we test new packages in updates-testing?
    What about new stuff in rawhide?
    How do you do installer testing?
    What do you do to test a new release (like Test1)?
    Get these things on the wiki or mailing list so we can discuss and improve them.
  4. QA tool updates - fedora-updates-system (lmacken), RHTS (poelstra/dmalcolm), SNAKE (wwoods)
    fedora-updates-system (lmacken)
    RHTS (poelstra/dmalcolm)
    SNAKE (wwoods)
  5. Anything else

Notes

log and notes never posted (2015-01-05).

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20061220&oldid=399873"