From Fedora Project Wiki

< QA‎ | Meetings

Revision as of 07:50, 4 April 2012 by Adamwill (talk | contribs) (update page with the results of the meeting)

Attendees

  • adamw (231)
  • VICODAN (105)
  • tflink (78)
  • j_dulaney (52)
  • kparal (47)
  • brunowolff (27)
  • Viking-Ice (8)
  • zodbot (6)
  • Southern_Gentlem (4)
  • jskladan (3)
  • pjones (2)
  • ianweller (1)
  • mkrizek (1)
  • satellit_ (1)
  • rbergeron (1)
  • j_dulaney1 (1)

Agenda

  • Previous meeting follow-up
  • Fedora 17 Beta status / blocker review
  • 'Project' status
  • Test Day report
  • Upcoming QA events
  • AutoQA update
  • Open floor

Previous meeting follow-up

  • kparal to propose revised criteria to cover split installs (installer sourced from one repo, packages from internet repos): didn't have a chance to do this yet
  • wwoods to ensure anaconda docs are updated to reflect what repo= is supposed to be capable of: wwoods was not around to update this

Fedora 17 Beta status / blocker review

  • We still haven't been able to spin an RC3
  • We have pretty good RC2 test coverage, just a couple of tests remain, we can knock those off today

Blocker review

  • AGREED: more information needed on #807510 to reach a determination of blocker status, tflink will test with his similar hardware
  • AGREED: #808029 is accepted as a beta blocker per the criteria as they stand; criteria modification proposal is pending but needs further discussion in light of the virt-install use case
  • AGREED: #808378 is accepted as NTH because 3.4 fixes several known bugs and we obviously would prefer testing of final to testing of an obsolete beta
  • AGREED: #809052 is a blocker per the virtualization and 'installed system should boot to working desktop' criteria, for the sufficiently common case of VM using cirrus as the graphics driver

'Project' status

  • See the on-list discussion
  • We're happy for QA to officially become a 'Fedora project', we will stick the drafted Governance section into the Wiki somewhere and let the board know we're happy to accept project status. This decision does not in any way influence the question of the QA/Bugzappers relationship

Test Day report

Upcoming QA events

AutoQA update

  • No news, team is busy with Beta testing

Open floor

IRC Log