From Fedora Project Wiki

< QA‎ | Meetings

m (Updated notes)
 
m (Updated notes ... more to come)
Line 1: Line 1:
= Attendees =
= Attendees =


People present (lines said)
* jlaska (174)
* wwoods (52)
* Oxf13 (52)
* adamw (50)
* kparal (28)
* Viking-Ice (13)
* Southern_Gentlem (11)
* lili_ (10)
* nirik (10)
* zodbot (8)
* mcepl (3)
* buggbot (2)
* mbonnet (2)
* notting (1)
* Jeff_S (1)


Regrets:
Regrets:
Line 33: Line 50:


* [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00382.html Proposed meeting agenda]
* [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00382.html Proposed meeting agenda]
* [FIXME meetbot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2009-10-19/fedora-meeting.2009-10-19-15.58.html meetbot summary]


== Preview Meeting follow-up ==
== Preview Meeting follow-up ==
Line 41: Line 58:
* jlaska will investigate the 5 anaconda F12Beta issues to determine when the failures were introduced
* jlaska will investigate the 5 anaconda F12Beta issues to determine when the failures were introduced


inprogress
INPRGRESS - Adam Williamson posted feedback during the beta release readiness meeting ''36 issues were marked as beta blockers prior to freeze, 16 after the freeze.''.  I am manually inspecting the bugs added to the blocker list after the freeze (Sept 31) to determine if there is a pattern.  So far, only 2 bugs took longer than 2 days to be escalated to the F12Beta blocker list.  More manual fiddling required


* jlaska to investigate packaging of israwhidebroken.com for production instance
* jlaska to investigate packaging of israwhidebroken.com for production instance
Line 51: Line 68:
https://fedorahosted.org/fedora-infrastructure/ticket/1733
https://fedorahosted.org/fedora-infrastructure/ticket/1733


== F-12-Beta RC1 QA strategy ==
== Beta test review ==


RC ISO images are available and posted to http://alt.fedoraproject.org/pub/alt/stage/.  However, we still have 1 unresolved anaconda bug on the blocker list (see {{bz|526899}}).  Denise informed the group that Dave Lehman was investigating this issue and should have an update this afternoon.
Jlaska asked the group for feedback on what worked and what needs improvement for how the team tracks blocker bugs and organizes testing.


Jlaska noted that Liam and Rui have already started executing to plan for tests that are not specific to the release candidate ISO media (see [[Test_Results:Fedora_12_Beta_RC1_Install]]).  Once we have confirmation on the final ISO media kit, Liam will announce to fedora-test-list and invite testers to contribute feedback into the wiki.
== AutoQA Updates from wwoods and kparal ==


== AutoQA update ==
=== rpmguard ===


Wwoods spent some time last week focusing on the preupgrade F-12-Beta blocking bug (see {{bz|526208}}).
== How_to_Debug_<component> Update from Viking-Ice ==


Focusing on a clean solution to provide a link to the autotest results on the autoqa-results emails and israwhidebroken.com front-end (see https://fedorahosted.org/autoqa/ticket/65).
Rjune assisted adamw in testing the use of a wiki template for future debugging pages
* https://fedoraproject.org/wiki/How_to_debug_Dracut_problems2
* https://fedoraproject.org/wiki/Template:How_to_debug2


Wwoods also  looking into posting critical path package list to the wiki - currently blocked since JSON doesn't allow edit/create pages.  Jlaska provided a link to something mmcgrath shared a while back (see http://git.fedorahosted.org/git/?p=fedora-data.git).  Wwoods noted this handles uploading to the trac instance, not mediawiki.
Adamw asked if someone would like to rename the existing [[:Category:Debugging]] pages to use the new format: ''How to debug <component> problems''.  Adamw also suggested changing the back-links to avoid double redirect issues on the wiki.  Jlaska agreed to rename the pages.


Jlaska noted he might need guidance from wwoods when it comes to how best to incorporate israwhidebroken.com into the product instance (from a package standpoint).  Wwoods noted that the content should correspond to the infrastructure turbogears SOP - http://fedoraproject.org/wiki/TurboGears_Infrastructure_SOP.
== Open floor - <your topic here> ==
 
=== Packagediff update ===
 
kparal has implemented a majority of the important rpm checks (see https://fedorahosted.org/autoqa/ticket/54#comment:2)


kparal taking project naming suggestions to replace the current ''packagediff'' name (candidates include: 'rpmguard', 'rpmjudge' or 'rpmblame')
=== CritPath testing ===


Some discussion followed on how best to incorporate kparal's script into autoqa.  Wwoods advised that the script should work by itself much like install.py and sanity.py do in current autoqa.  From there, just create a wrapper script to handle the integration with autotest.
Oxf13 asked for extra eyes/fingers as crit-path tag requests come in for final.  Adam asked whether the process for requesting a post-Beta tag was documented.


== How_to_Debug_<component> wiki pages ==
=== Common_F12_Bugs ===


Viking_Ice started a great discussion around how best to improve the current Category:Debugging content - https://www.redhat.com/archives/fedora-test-list/2009-October/msg00112.html
Adamw reminded the group, ''if you're aware of any bug that's in the released beta images that you think should be documented there, please either add it (there's guidelines on layout in the wiki page source) or add the 'CommonBugs' keyword to the bug report.''


A proposed template exists for use as a guide for all future pages (see [[Template:How_to_debug]])
* [http://tinyurl.com/l4kma5 Bugs that need Common_F12_Bugs documentation]


Viking-Ice would like feedback on a naming convention for future pages.  Candidates include: "How to debug <component>". or "component <component> problems" or "bug info <component>".  Viking-Ice noted that campbecg helped define the different pages as:
=== rats_install still failing ===


  As a reporter, looking at the wiki, I would see a page called "Bug Info ComponentX" and
Jlaska asked if there were any updates on the download.fedora.devel.redhat.com rsync from download.fedoraproject.org.  It appears autoqa rats_install results are still failing due to bad content on the download site (see https://fedorahosted.org/pipermail/autoqa-results/2009-October/001654.html).
  expect a page relating to known bugs on componentx, a page called "ComponentX Problems"
  to be full of known issues related to using componentx, and "How to Debug ComponentX"
  at a howto about how to actually debug it"


Both gtirloni and jlaska confirmed and agreed that the ''How to debug <component'' scheme made the most sense and that changes could be made as needed, but felt there was enough information available to start fleshing out additional pages.  Viking-Ice noted he would investigate markmc's Virtualization bug reporting page next.
=== F-12 Talking Awesomeness talking points ===


== Open floor - <your topic here> ==
Adamw recommended [[F12_Beta_Announcement]] for folks looking for talking points about what's new in Fedora 12.


== Upcoming QA events ==
== Upcoming QA events ==
Line 100: Line 112:


= Action items =
= Action items =
* jlaska to rename other debug pages (see https://fedoraproject.org/wiki/Category:Debugging) to be consistent with "How to debug <component> problems". Update back-links also


= IRC transcript =
= IRC transcript =

Revision as of 19:16, 19 October 2009

Attendees

People present (lines said)

  • jlaska (174)
  • wwoods (52)
  • Oxf13 (52)
  • adamw (50)
  • kparal (28)
  • Viking-Ice (13)
  • Southern_Gentlem (11)
  • lili_ (10)
  • nirik (10)
  • zodbot (8)
  • mcepl (3)
  • buggbot (2)
  • mbonnet (2)
  • notting (1)
  • Jeff_S (1)

Regrets:

  • He Rui (rhe)


Agenda

Preview Meeting follow-up

QA/Meetings/20091012#Action_items

  • jlaska will investigate the 5 anaconda F12Beta issues to determine when the failures were introduced

INPRGRESS - Adam Williamson posted feedback during the beta release readiness meeting 36 issues were marked as beta blockers prior to freeze, 16 after the freeze.. I am manually inspecting the bugs added to the blocker list after the freeze (Sept 31) to determine if there is a pattern. So far, only 2 bugs took longer than 2 days to be escalated to the F12Beta blocker list. More manual fiddling required

  • jlaska to investigate packaging of israwhidebroken.com for production instance

Packaged thanks to python setuptools. Need to determine whether to incorporate into autoqa now. Wwoods had the suggestion of creating a autoqa/front-ends directory to include this and other "Is <component> broken?" front-ends.

  • jlaska to request autoqa-devel@ for autoqa development discussion and patch review

https://fedorahosted.org/fedora-infrastructure/ticket/1733

Beta test review

Jlaska asked the group for feedback on what worked and what needs improvement for how the team tracks blocker bugs and organizes testing.

AutoQA Updates from wwoods and kparal

rpmguard

How_to_Debug_<component> Update from Viking-Ice

Rjune assisted adamw in testing the use of a wiki template for future debugging pages

Adamw asked if someone would like to rename the existing Category:Debugging pages to use the new format: How to debug <component> problems. Adamw also suggested changing the back-links to avoid double redirect issues on the wiki. Jlaska agreed to rename the pages.

Open floor - <your topic here>

CritPath testing

Oxf13 asked for extra eyes/fingers as crit-path tag requests come in for final. Adam asked whether the process for requesting a post-Beta tag was documented.

Common_F12_Bugs

Adamw reminded the group, if you're aware of any bug that's in the released beta images that you think should be documented there, please either add it (there's guidelines on layout in the wiki page source) or add the 'CommonBugs' keyword to the bug report.

rats_install still failing

Jlaska asked if there were any updates on the download.fedora.devel.redhat.com rsync from download.fedoraproject.org. It appears autoqa rats_install results are still failing due to bad content on the download site (see https://fedorahosted.org/pipermail/autoqa-results/2009-October/001654.html).

F-12 Talking Awesomeness talking points

Adamw recommended F12_Beta_Announcement for folks looking for talking points about what's new in Fedora 12.

Upcoming QA events

  • 2009-10-12 - F12 Beta go/no_go meeting (@ 18:00pm - rel-eng meeting)
  • 2009-10-13 - BugZappers/Meetings
  • 2009-10-14 - Beta Project Wide Release Readiness Meeting
  • 2009-10-15 - i18n Test Day

Action items

IRC transcript

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