Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47341
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <7f3ed2c31003161123p66e59b0h369afdfd35b0caca@mail.gmail.com>
Date: Tue, 16 Mar 2010 22:12:01 +0100
Cc: Derick Rethans <derick@derickrethans.nl>,
 PHP Developers Mailing List <internals@lists.php.net>,
 Scott MacVicar <scottmac@php.net>,
 Ilia Alshanetsky <ilia@php.net>,
 =?iso-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <AA904E48-1218-4131-9CA0-FCAFE47EE2B8@pooteeweet.org>
References: <alpine.DEB.2.00.1003161545500.4153@kossu.derickrethans.nl> <7f3ed2c31003161123p66e59b0h369afdfd35b0caca@mail.gmail.com>
To: Hannes Magnusson <hannes.magnusson@gmail.com>
Subject: Re: [PHP-DEV] PHP 5.4 branch and trunk
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 16.03.2010, at 19:23, Hannes Magnusson wrote:

> On Tue, Mar 16, 2010 at 16:58, Derick Rethans =
<derick@derickrethans.nl> wrote:
>> Before we add features, they need to be discussed whether we want to
>> have them.
>=20
> Does that mean you want to take up a
> - strict RFC-and-after-3months-discussion-before-commit policy
>  (i.e. killing the scratching-an-itch spirit of PHP)
> - "I'm going to commit this patch tomorrow" mail to internals@
>  (i.e. killing "I need this functionality, maybe others do to" spirit =
of PHP)

Its all a question about the scope of the change obviously. There is =
some tipping point where it makes sense for an RFC. Remember an RFC not =
only serves decision making, but also provides some level of =
documentation (on which the final documentation can be build) for past =
generations (this is why I for example wrote the ifsetor RFC after we =
decided that we cannot currently implement it).

So like Stas said .. common sense still rules.

> I would much rather have a development branch which ""everything
> goes"" (like it used to) and then make it up to the release manager to
> merge the features he wants in "his branch" (DVCS style)

I dont think we ever had an "everything goes" HEAD .. lets say in the =
past we had a small very active core dev team with really short turn =
around times for decisions because everybody was answering on IRC or =
mailinglists within minutes. As a result decisions (not always for the =
better) were made in a much shorter timeframe than the current =
availability of core developers affords us.

>> - Ilia's scalar type hint patch.
>=20
> And which of Ilias patches are you referring to? The original one
> (which is identical to the patch I sent in November 2006) or the
> "fucking eyh, I need to please everyone so this can be in 5.3 - but
> still got rejected" patch?

I think he clearly pointed to the wiki page which lists 3 proposals. He =
is just suggesting we should finalize which one we want and get it in.

> You didn't even list the mbstring patch.. that was discussed and as
> far as I remember everyone thought it was great idea, just not in a
> stable branch.


Is this tone really necessary? One you are argueing for more flexibility =
and then you are shooting the messenger because in a long list he forgot =
one thing (there are probably a few others .. we might want to go =
through the todo wiki pages for more)?

regards,
Lukas Kahwe Smith
mls@pooteeweet.org