From Fedora Project Wiki

< QA‎ | Meetings

(Add nirik discussion topic)
 
(Initial agenda)
Line 1: Line 1:
= Attendees =
People present (lines said):
Unable to attend:
# [[User:Liam|Liam]]
# [[User:Rhe|Rhe]]
# [[User:Newgle1|Newgle1]]
= Agenda =
= Agenda =
* [http://lists.fedoraproject.org/pipermail/test/2010-August/092761.html Proposed meeting agenda]
* [FIXME MeetBot summary]
== Previous meeting follow-up ==
# jlaska to inquire how frequently boot.fp.org gets updated F-14 install images
# 621864 - jlaska to check-in with skvidal to see whether potential_conflict.py script updates are required for proper %ghost handling
# 622058 - jlaska to ping mgracik for guidance on pending firstboot changes
== F14 Alpha test milestones ==
; Owner - [[User:rhe|rhe]], [[User:adamwill|adamwill]]
; Summary
: F-14 Alpha RC#4 compose CD and DVD images are available for test (see https://fedorahosted.org/rel-eng/ticket/3856)
: 1 blocker bug remains (see below)
; Next steps...
: Continue posting test results ([[Test_Results:Current_Installation_Test|installer]] or [[Test_Results:Current_Desktop_Test|desktop]])
: Review blocker bugs
:: {{bz|596985}} (MODIFIED) ''hang at start of X11 on fresh install from DVD''
= Open discussion - <Your topic here> =


== Developing action plans for [[Updates_lessons]] ==
== Developing action plans for [[Updates_lessons]] ==
Line 7: Line 35:
: I setup [[Updates_Lessons]] as part of implementing the boards updates vision thing. We talked today about looking at and learning from updates issues. Would it be reasonable to file a ticket with qa track anytime there is a new update issue and then discuss it in qa how to learn from or prevent it? or would you want fesco to discuss that kind of thing.
: I setup [[Updates_Lessons]] as part of implementing the boards updates vision thing. We talked today about looking at and learning from updates issues. Would it be reasonable to file a ticket with qa track anytime there is a new update issue and then discuss it in qa how to learn from or prevent it? or would you want fesco to discuss that kind of thing.
; Next steps...
; Next steps...
= Upcoming QA events =
* 2010-07-29 - [[:Category:Fedora_14_Alpha_TC_Test_Results|Test Alpha 'Test Compose']]
* 2010-07-30 - [http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-30/blocker-review.2010-07-30-16.00.html Alpha Blocker Meeting (f14alpha) #3]
* 2010-08-05 - [[:Category:Fedora_14_Alpha_RC_Test_Results|Test Alpha Candidate]]
* 2010-08-06 - [http://meetbot.fedoraproject.org/fedora-bugzappers/2010-08-06/fedora_14_alpha_blocker_review.2010-08-06-16.01.html Alpha Blocker Meeting (f14alpha) #4]
* 2010-08-11 - Fedora 14 Alpha Go/No-Go Meeting (17:00 EST) -- introduced '''1 week schedule slip'''
* 2010-08-18 - Fedora 14 Alpha Go/No-Go Meeting (17:00 EST)
* 2010-08-24 - Alpha Public Availability
= Action items =
# adamw and jlaska to propose artwork final release criteria
= IRC Transcript =

Revision as of 13:05, 16 August 2010

Attendees

People present (lines said):

Unable to attend:

  1. Liam
  2. Rhe
  3. Newgle1

Agenda

Previous meeting follow-up

  1. jlaska to inquire how frequently boot.fp.org gets updated F-14 install images
  2. 621864 - jlaska to check-in with skvidal to see whether potential_conflict.py script updates are required for proper %ghost handling
  3. 622058 - jlaska to ping mgracik for guidance on pending firstboot changes

F14 Alpha test milestones

Owner - rhe, adamwill
Summary
F-14 Alpha RC#4 compose CD and DVD images are available for test (see https://fedorahosted.org/rel-eng/ticket/3856)
1 blocker bug remains (see below)
Next steps...
Continue posting test results (installer or desktop)
Review blocker bugs
RHBZ #596985 (MODIFIED) hang at start of X11 on fresh install from DVD

Open discussion - <Your topic here>

Developing action plans for Updates_lessons

Owner - nirik
Summary
I setup Updates_Lessons as part of implementing the boards updates vision thing. We talked today about looking at and learning from updates issues. Would it be reasonable to file a ticket with qa track anytime there is a new update issue and then discuss it in qa how to learn from or prevent it? or would you want fesco to discuss that kind of thing.
Next steps...

Upcoming QA events

Action items

  1. adamw and jlaska to propose artwork final release criteria

IRC Transcript