From Fedora Project Wiki
(Add links to installer builds and another recommended 'what to do different?') |
|||
| Line 27: | Line 27: | ||
* Verify that desired anaconda version is available the day before compose | * Verify that desired anaconda version is available the day before compose | ||
* Coordinate with installer lead several weeks prior | * Coordinate with installer lead several weeks prior | ||
* Create a checklist of reminders and dependencies that should be confirmed prior to the compose date? | |||
* 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 14:18, 13 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 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 |
Could Have Been Better
| Task | Date | What Happened? | What To Do Differently Next Time? |
|---|---|---|---|
| Create Installable Images for QA testing #1 | 2010-07-08 |
|
|