On Wed, Nov 12, 2008 at 12:03 PM, Jeff Spaleta <jspaleta@xxxxxxxxx> wrote: > On Wed, Nov 12, 2008 at 9:46 AM, Jeremy Katz <katzj@xxxxxxxxxx> wrote: >> Otherwise, we're really saying that the release date of release n+1 is >> release n's date + six months (which is what we used to do). And the >> problem with that is that any slips over time meaning that we end up >> running into major holidays for a release date and have to have a >> long/short cycle to reset things. > > Does it make sense to ask the following questions? > > Historically, how much do we tend to slip per release? Disregarding > the month during F10 run up specifically during the infrastructure > rebuild. Are we somewhat consistent with regard to slippage? Is there > an average slippage? The sample size is pretty small so I admit its > not a statically valid measure. What's the most we've slipped in the > past, that is not the direct result of significant system downtime? > > Accounting for historical slippage, were does F12 release land? Mid Nov? > Historically, Red Hat Linux missed a internal and external ship date by 2 weeks to 1 month pretty consistently. Fedora seems about the same. Some of it was because 'stuff happens' and some of it was that a some set of people don't get serious about something until the deadline starts looming.Those people's effects have a trickle down effect which usually adds up to a slip. I think the closest RH came to an on target release was when everyone in development was told that X was the ship date and Y turned out to be what management expected. X was missed by Y was hit. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" _______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board
