Continue tracking specific bugs and packages that are out of band of the stable branch and need to be manually included by recording them in the Trac ticket.

This provides transparency to all the people working on the process and lessens the chance of something being missed.

Save time having to recompose if if something is missed.

Beta Test Compose

2010-09-09

Completed on schedule

Maintain good communication with Anaconda team and other critical path packages pertinent to the release

Enhance schedule for Anaconda team as requested

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.

In the absence of information from the maintainer the meeting is held up while various people try to research the problem and group discussion attempts to fill in information gaps--many times this works, but it is incredibly inefficient without the package maintainer present.

IRC communication can be laggy and disorganized

Review and hound maintainers for information about bugs in the comments of proposed and approved blocker bugs as soon as they come in--don't wait for Friday's meeting

Use Fedora Talk (conferencing system) to speed up discussion and keep meeting more focused

stream audio to the web

people without the ability to connect to Fedora Talk can listen to web stream and respond in IRC

Branch Fedora 14

2010-07-27

Completed on 2010-07-29

New boost package landed on 2010-07-27

Python rebuild to 2.7 took longer than expected

Change from CVS to Git

Assume that branching takes more than one day?

Fedora 14 Alpha Test Compose

2010-07-29

Test Compose #1 produced on 2010-08-01. Does not boot because of bug 602274

Test Compose #2 produced on 2010-08-03. Cannot install because of bug 620900

Gave up on Test Compose #3 and moved to preparing for the Release Candidate

Smash less major changes together at the same time: python 2.7, changing SCM, systemd

Could we do any sanity testing before publishing images to make sure they boot to save bandwidth and turn around time? In the case of Test Compose #1 it fell over right way.

Kevin Kofler suggests it may ultimately have worked out better simply to delay the Alpha freeze and leave dist-f14 tag open until the major problems were resolved

Feature Submission Deadline

2010-07-13

It isn't obvious that spins are included in this item, and hence are due before this date.

Seems that spin deadline could be later, there is so much other stuff eg even the main Fedora gnome/kde spins to test. (The current spins wrangler disagrees.)

Concentrate on one spin successful booting

Set a slightly or much later spin completion date

Nightly Spin composes

2010-07-*

soname bumps broke a number of the spins that made it difficult to test spins and that cascaded into discovering several bugs very close to the alpha freeze and a lot of scrambling to solve then in a short period of time.

Get features that impact lots of other packages (or testing thereof) in well before the deadline.

Nightly Spin ISOs for Alpha

2010-08-24

Overlapping issues with broken dependencies have resulted in the Games Spin not composing since July 27th at which point the Splash Screen bug (617115) still existed in livecd-tools. So the Games Spin ISO that exists at the Alpha release will be unusable.

Mirrors may have gotten word late about the F14 Alpha content availability, compared to previous releases. A notice was sent 24 hours ahead (subscriber only link). Only about 50% of the mirrors included F14 Alpha content by 1400 UTC 2010-08-24, which may have been related. Usually the mirror list is notified the Friday before the release.

Include a task on the schedule going forward to include making this announcement.

Include the actual procedure in the automatically filed rel-eng Trac ticket for releases.