Fedora 14 Schedule Retrospective

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Could Have Been Better)
(Could Have Been Better)
Line 28: Line 28:
 
* 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?
 
* Create a checklist of reminders and dependencies that should be confirmed prior to the compose date?
 +
* Send a reminder to devel-announce to have packages in ''rawhide'' for upcoming 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 11:59, 14 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
  • Not ready until 2010-07-12
  • Installer lead was out during week, backup built anaconda-14.10-1.fc14 and pykickstart-1.76-1.fc14 in rawhide on 2010-07-08
  • Release Engineering lead was on out on 2010-07-09
  • Koji Outage 2010-07-10 to 2010-07-11
  • Verify that desired anaconda version is available the day before compose
  • Coordinate with installer lead several weeks prior
  • Create a checklist of reminders and dependencies that should be confirmed prior to the compose date?
  • Send a reminder to devel-announce to have packages in rawhide for upcoming compose
  • Build up the Release Engineering team so that alternate team members can compose releases