slowing down the development schedule for a release.

Josh Boyer jwboyer at
Wed Aug 21 01:09:03 UTC 2013

On Tue, Aug 20, 2013 at 8:57 PM, Matthew Miller
<mattdm at> wrote:
> On Tue, Aug 20, 2013 at 06:47:31PM -0500, Dennis Gilmore wrote:
>> I need to update the documentation. But we need to get to the point
>> where the releng side is transparent and just happens. The crazy
>> schedules we have had since f18 have allowed zero time for Release
>> Engineering and QA to do much in the line of development. this is
>> entirely a failure of FESCo
> Without spinning the wheel of blame -- at Flock, we talked about slowing
> down the crazy train a little bit, probably not for F20 at this point but
> for F21, specifically so we all have a chance to work on those kind of
> things.

Why not F20?  FESCo perpetuated the "we don't have a schedule yet so
we'll do the Not-Before-XXX-Date thing" long enough that it's
certainly able to do so to extend the schedule.  I fail to see the
point in forcing an F20 schedule that various parties think is crazy
just for the sake of sticking to some nebulous dates.  If you're wary
of the holiday break (which you should be), then push it out well past

Continuing to think that we're going to fix the release schedule
problems with the Next release is clearly not working.


More information about the devel mailing list