Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102720
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVoRW7kovTAPPqb1PBbrabtbwR==ZW8QSGoeFWBzS68-sQ@mail.gmail.com>
References: <CAESVnVoRW7kovTAPPqb1PBbrabtbwR==ZW8QSGoeFWBzS68-sQ@mail.gmail.com>
Date: Tue, 10 Jul 2018 19:36:53 +0300
Message-ID: <CAPhkiZxLqhtVk+JN0BL-L1zpTbEx7FAFbiLX4CC0cRGh-WaWgQ@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] On not rushing things at the last minute
From: narf@devilix.net (Andrey Andreev)

Hi,

On Tue, Jul 10, 2018 at 4:10 PM, Sara Golemon <pollita@php.net> wrote:
> I'm disappointed by the last minute kitchen-sink dump of RFCs being
> raised, rushed through discussion, and voted on with minimal periods.
> While I'm all for delivering useful features to end users, I don't
> want us to get in the habit of seeing months of quiet followed by
> weeks of chaos every year around this time.  This isn't even new,
> though it seems like it's becoming more commonplace with the adoption
> of the yearly cadence.
>
> What are the causes?
>

Aside from life keeping you busy until you realize it's that time of
the year again, I believe it's just the short development cycle and is
no coincidence that this has been happenning more often since getting
into a yearly schedule.

In my observation, adoption rates are slower than the release cycle
and so it's kind of like ... I barely got to enjoy the shiny new thing
and the next feature freeze is already happening. And then also, we're
always eager to get our idea in before feature freeze, but that's hard
to achieve unless we come up with it in January or earlier, but since
everybody's naturally got their eyes set on version.next, few people
think about X.Z before X.Y is released.

I don't know if this can be fixed though. It's just hard to keep up
with schedules on side projects and let's face it - PHP is nobody's
primary job, so any work spent on it is by definition a side project.

Cheers,
Andrey.