From Fedora Project Wiki
| Line 23: | Line 23: | ||
* Anaconda did not land in rawhide until 2010-07-08 | * Anaconda did not land in rawhide until 2010-07-08 | ||
* Release Engineering lead was on out on 2010-07-09 | * Release Engineering lead was on out on 2010-07-09 | ||
* Koji Outage 2010-07-10 to 2010-07-11 || | * Koji Outage 2010-07-10 to 2010-07-11 | ||
|| | |||
* Verify that desired anaconda version is available the day before compose | * Verify that desired anaconda version is available the day before compose | ||
* Build up the Release Engineering team so that alternate team members can compose releases | * Build up the Release Engineering team so that alternate team members can compose releases | ||
|- | |- | ||
|} | |} | ||
Revision as of 21:50, 12 July 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 Happened? | How to Repeat It? |
|---|---|---|---|
Could Have Been Better
| Task | Date | What Happened? | What To Do Differently Next Time? |
|---|---|---|---|
| Create Installable Images for QA testing #1 | 2010-07-08 |
|
|