-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 21 Aug 2013 07:37:10 -0400
Josh Boyer <jwboyer(a)fedoraproject.org> wrote:
On Wed, Aug 21, 2013 at 3:12 AM, Dennis Gilmore
<dennis(a)ausil.us>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 20 Aug 2013 23:37:44 -0400
> Matthew Miller <mattdm(a)fedoraproject.org> 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.
As far as I know, we've done a mass rebuild and we've branched. FESCo
has closed the Changes. Beyond that, I don't know what else has
actually started. Can you elaborate?
Physically it can be done, now that we have branched it means we would
have two development strains for awhile or we have a pain point
somewhere. biggest issue is that FESCo set an expectation that a
release will happen this year. all the hand waviness around dates
doesn't relate to reality. Again my thoughts may be wrong but I don't
think so.
Also, while there might be many tasks started, I don't really
remember
them having strict time windows. Pushing out all the dates starting
today seems feasible to me. Clearly it can be done, because we keep
slipping every release and we still have releases.
not having strict time windows is a new thing. Setting a date sets an
expectation. There is big pain for all with slipping.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlIUu14ACgkQkSxm47BaWfeP4wCgkMgaLHPLyvAzb6kbuKO/M92A
MJMAnjg37ZqII7ZBHd55yxxeAJrDQH5A
=e2gP
-----END PGP SIGNATURE-----