The slip down memory lane

John Poelstra poelstra at redhat.com
Mon Aug 16 21:38:32 UTC 2010


Adam Williamson said the following on 08/13/2010 05:21 PM Pacific Time:
> On Thu, 2010-08-12 at 16:11 -0600, Linuxguy123 wrote:
>
>> On the data side, it would be very interesting to go back to each one of
>> those slips and identify the component(s) that caused the slip and then
>> question the individuals behind them to find out what happened.  Then
>> take that information (share it with the list ?) and see what can be
>> concluded (as a group ?)
>
> This would be incomplete data.
>
> For instance, the bug we decided to slip Alpha for was the 'basic video
> driver' menu entry in the installer not working. But that's not
> necessarily the entire cause of the slip. If the entire release process
> had run on time, and we'd had really testable candidate images earlier
> than we did, it's entirely possible this bug would have been identified
> and fixed in time for the Alpha to be shipped.
>
> Just looking at the specific bugs that end up blocking the release does
> not give a complete picture of why the release slipped.

Well put.  All the incremental steps along the road are documented here 
for Fedora 14.

https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective

Each piece adds up to the point were we just can't finish in the 
allotted time.

Anecdotally, what happened in this release is not unusual.  Each release 
we have these "this shouldn't ever happen again" items and while they 
have different names the reasons are almost always the same--landing 
changes to packages or infrastructure right on the deadline or not 
budgeting enough time to recover before the deadline if something goes 
wrong.

It would be great to get more entries from other people on this wiki 
page.  Please don't send them to the list, but put them on the wiki page.

John


More information about the devel mailing list