From Fedora Project Wiki
Line 130: | Line 130: | ||
* If possible include the time of meetings in the ical schedule - so they appear at right time/date in calendars. | * If possible include the time of meetings in the ical schedule - so they appear at right time/date in calendars. | ||
|- | |- | ||
| Compose Beta RC || 2010-09-16 || RC compose was not ready until the end of 2010-09-17 because of two un-resolved blocker bugs (anaconda and kernel). Both bugs had been open for several days. || Determine if one week is really enough time from the creation of the ''Test Compose'' and ''Release Candidate''--during which time we need to test the Test Compose, identify bugs, fix bugs, and the then compose ''Release Candidate.'' | |||
|- | |||
<!-- | Task || Date || What Happened? || What To Do Differently Next Time? --> | <!-- | Task || Date || What Happened? || What To Do Differently Next Time? --> | ||
|} | |} |
Revision as of 00:02, 18 September 2010
Background
Largely inspired by the success Fedora 13 QA Retrospecitve and the benefit of capturing data from ideas and events when they happen, this page is for tracking Fedora 14 schedule successes and mis-steps. It's goal is iteratively track and refine our process of testing and releasing Fedora 14 on time.
Any Fedora team member or community observer is welcome to add information here.
Successes
Task | Date | What was successful? | How to Repeat It? |
---|---|---|---|
Pre-Alpha Rawhide Acceptance Test Plan #1 | 2010-07-12 | Anaconda traces back on install. The success here is that we discovered this problem four weeks before the Alpha Compose | Keep doing what we are doing |
Pre-Alpha blocker bug meetings | 2010-07-24 | Meetings are happening each week and people are referencing the release criteria in the bugs--this is helping to save time at the review meetings |
|
Compose Alpha Release Candidate | 2010-08-05 |
|
|
Tracking release blockers | 2010-08-05 |
|
|
Beta Test Compose | 2010-09-09 | Completed on schedule |
|
Tracking Compose Details | 2010-09-14 | We are tracking more and more detail in the release engineering tickets for each official compose, in particular which packages must be in as demonsrated in this ticket. This makes the process more transparent and allows more eyes on the details increasing the chances of getting things right the first time. | Continue to track important package details and instructions for the compose in the Trac ticket. |
Blocker Bug Meetings | 2010-09-14 | Holding weekly blocker bug meetings each Friday and monitoring the the blocker bug list closely and having an additional ad-hoc meeting on the Tuesday before the Thursday RC Compose to make sure everything was moving in the right direction. | More of the same |
Could Have Been Better
Task | Date | What Happened? | What To Do Differently Next Time? |
---|---|---|---|
Create Installable Images for QA testing #1 | 2010-07-08 |
|
|
Create Installable Images for QA testing #3 | 2010-07-22 |
|
|
Fedora 14 Blocker Meetings are already taking a minimum of an hour | 2010-07-24 |
|
|
Branch Fedora 14 | 2010-07-27 |
|
|
Fedora 14 Alpha Test Compose | 2010-07-29 |
|
|
Feature Submission Deadline | 2010-07-13 |
|
|
Nightly Spin composes | 2010-07-* |
|
|
Nightly Spin ISOs for Alpha | 2010-08-24 |
|
|
Notify mirrors about new release content | 2010-08-23 |
|
|
Web content change for F14 Alpha | 2010-08-24 |
|
|
Meeting times | 2010-08-31 |
|
|
Compose Beta RC | 2010-09-16 | RC compose was not ready until the end of 2010-09-17 because of two un-resolved blocker bugs (anaconda and kernel). Both bugs had been open for several days. | Determine if one week is really enough time from the creation of the Test Compose and Release Candidate--during which time we need to test the Test Compose, identify bugs, fix bugs, and the then compose Release Candidate. |