Re: slowing down the development schedule for a release.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 21, 2013 at 9:12 AM, Dennis Gilmore <dennis@xxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 20 Aug 2013 23:37:44 -0400
> Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
>
>> On Tue, Aug 20, 2013 at 09:09:03PM -0400, Josh Boyer wrote:
>> > > 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
>>
>> Um, I asked Dennis and he said it was too late for that to be useful.
>> So there's that. :)
>
> we have already started so many of the release processes that it is
> really hard to stop and postpone things.  not impossible, just makes
> things very difficult. We started on the tasks for fedora 20 about a
> week after f19 was done due to the schedule that was setup.

The whole discussion does not make much sense unless we know what you
exactly want to do, how much time you need for it and why it can't be
done during a release cycle and deployed for the next release.
Currently this reads like "I need more time to do something".
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux