From Fedora Project Wiki
(create initial page for 06-18 meeting) |
(add some retrospective discussion) |
||
| Line 4: | Line 4: | ||
* Previous meeting follow-up | * Previous meeting follow-up | ||
* ARM as a primary arch | * ARM as a primary arch | ||
* Fedora 17 retrospective | |||
* AutoQA update | * AutoQA update | ||
* Open floor | * Open floor | ||
| Line 14: | Line 15: | ||
== ARM as a primary arch == | == ARM as a primary arch == | ||
== Fedora 17 retrospective == | |||
* RC schedule tinkering: should we aim for RC on Tuesday? What's the plan for Go/No-Go and Release Readiness meetings this cycle? | |||
* Blocker bug meetings: should we move them from Fridays? | |||
* How can we analyze the blocker bug lists for useful data? Bruno "I think it would be useful to review the blocker bugs to see if we can spot any trends. Just looking at the component counts might be useful. even if we don't do anything more." | |||
== AutoQA update == | == AutoQA update == | ||
Revision as of 01:05, 13 June 2012
Attendees
Agenda
- Previous meeting follow-up
- ARM as a primary arch
- Fedora 17 retrospective
- AutoQA update
- Open floor
Previous meeting follow-up
- adamw to review F17 retrospective and come up with an action plan
- adamw to work with rbergeron to make sure housekeeping gets done for f16/f17/f18
- tflink to fix up blocker bug page for new bugzilla, probably as fedora-hosted static HTML rather than in MW
- tflink to set up QA git account
ARM as a primary arch
Fedora 17 retrospective
- RC schedule tinkering: should we aim for RC on Tuesday? What's the plan for Go/No-Go and Release Readiness meetings this cycle?
- Blocker bug meetings: should we move them from Fridays?
- How can we analyze the blocker bug lists for useful data? Bruno "I think it would be useful to review the blocker bugs to see if we can spot any trends. Just looking at the component counts might be useful. even if we don't do anything more."