As seen on the official announcement list, the final release of Fedora 13 will be postponed by a one-week slip. As the announcement notes, the blocker bug list is not empty, which means that according to our F13 final release criteria, we slip the release.
It’s always disappointing when we don’t hit our original target, but these criteria allow us to focus on objective markers to measure our readiness. It was a pleasure sitting in that readiness meeting tonight with some very smart people, because it was focused on the worthy goal of dispassionately measuring our status based on the ruler we’ve set for ourselves.
I suspect as we go we’ll need to tune release criteria in certain areas where we want more detail. Tonight, for intance, we found there was at least one place where the written criteria could be clearer about their intent. There is a retrospective scheduled for QA after the release of Fedora 13, at which we can note some of the discrepancies and tune as needed.
This iterative approach has worked very well for our release schedule, which I’d really like to see us let stand for a few releases, as we consider other changes. Thanks to all of the people who participate in the process — the teams of people working on QA, Release Engineering, Anaconda, kernel, and countless other packages for our release. The collaboration that’s gone on this release has been tremendous, and Fedora 13 is shaping up to be spectacular as a result!
Pingback: Paul W. Frields: Schedule change. | TuxWire
Pingback: Fedora 13 End Game Part 2 « John Poelstra