Am 24.10.2017 um 06:07 schrieb Kalle Sommer Nielsen:
Dear Internals
I have in the past few days been working on, and I continue to work on
cleaning up our bug tracker. We are close to 5000 open bugs[1], while
about 1500 of those are FR requests, some opened as far back as
2001[2]
but why do
>
> Hi!
>
> > It's not terribly unreasonable IMO, but before I just writeup the RFC
> > as described (jsonRawSerialize taking preceedence over jsonSerialize),
> > I thought I'd ask for opinions on the specifics.
> >
> > In psuedo-code:
> >
> > if (is_object($obj)) {
> > if ($obj implements JsonRa
Hi Kalle,
> Currently I'm going over every single report to try classify them,
> close reports which would require an RFC, PECL packages with no
> releases for literally years and unassign people from bug reports
> which have not been active (committed) in a long time, or similar.
I did somethi
Hi Christopher,
> I like the added flexibility in placement of the end token, but I think
> requiring only tabs or spaces, and stripping whitespace from all {here|now}doc
> lines is error prone and adds unnecessary complexity.
I agree that the requirement for using either tabs or spaces is not
Hi Kalle,
On 24 October 2017 at 05:07, Kalle Sommer Nielsen wrote:
> Dear Internals
>
> I have in the past few days been working on, and I continue to work on
> cleaning up our bug tracker.
While that's good overall - I think assigning documentation bugs to
people is not so good.
Documentation
On Tue, Oct 24, 2017 at 11:27 AM, Thomas Punt wrote:
> Hi Christopher,
>
>
> > I like the added flexibility in placement of the end token, but I think
> requiring only tabs or spaces, and stripping whitespace from all
> {here|now}doc
> > lines is error prone and adds unnecessary complexity.
>
> I
On 31 August 2017 at 02:30, Kris Craig wrote:
> Why would they need to be synced?
Currently Imagick can have a single branch. Commits to that branch are
made and then for the next release, we can determine if it needs to be
a major minor or patch release based on the changes.
People are then fr
On 15 August 2017 at 14:04, Dan Ackroyd wrote:
> Actually, it would be lovely if anyone contributed to Imagick.
So far, no volunteers. :-p
As well as the documentation that are open, this bug:
https://bugs.php.net/bug.php?id=73840
Is one that doesn't require any knowledge of ImageMagickit
On Mon, Oct 23, 2017 at 10:07 PM, Anatol Belski wrote:
> Hi Jakub,
>
> > -Original Message-
> > From: jakub@gmail.com [mailto:jakub@gmail.com] On Behalf Of
> Jakub
> > Zelenka
> > Sent: Monday, October 23, 2017 10:43 PM
> > To: Anatol Belski
> > Cc: internals@lists.php.net
> > Su
On Tue, Oct 24, 2017 at 7:32 AM, Stanislav Malyshev
wrote:
> Hi!
>
> > It's not terribly unreasonable IMO, but before I just writeup the RFC
> > as described (jsonRawSerialize taking preceedence over jsonSerialize),
> > I thought I'd ask for opinions on the specifics.
> >
> > In psuedo-code:
> >
On 7 October 2017 at 19:34, Sammy Kaye Powers wrote:
> Hello internals friends!
>
> The RFC to allow a trailing comma in function calls is up for discussion:
>
> https://wiki.php.net/rfc/trailing-comma-function-calls
>
> Summary:
>
> - Targets PHP 7.3
> - The previous vote on this combined functi
On Tue, Oct 24, 2017 at 11:37 AM, Peter Cowburn wrote:
> I know it's late in the game, but I have a quick question. This RFC
> includes a couple of "Not really a function" functions (namely isset() and
> unset()) that will also be able to have a trailing comma, but I'm failing
> to find the discus
On 10/24/2017 2:20 AM, Sara Golemon wrote:
> https://bugs.php.net/bug.php?id=75400 is asking for a version of
> JsonSerializable which doesn't involve deserializing/reserialzing
> round trips when a chunk of JSON is known in advance.
>
> It's not terribly unreasonable IMO, but before I just writeu
Hi Jakub,
> -Original Message-
> From: jakub@gmail.com [mailto:jakub@gmail.com] On Behalf Of Jakub
> Zelenka
> Sent: Tuesday, October 24, 2017 3:54 PM
> To: Anatol Belski
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC] PCRE2 migration
>
>
>
> On Mon, Oct 23, 2017 a
On 24/10/17 8:27 pm, Thomas Punt wrote:
Hi Christopher,
> I like the added flexibility in placement of the end token, but I think requiring only tabs or spaces, and stripping whitespace from all
{here|now}doc
> lines is error prone and adds unnecessary complexity.
I agree that the require
15 matches
Mail list logo