I personally agree with the idea of targeting 7.0 and up, Larry made a good
case for it.
Release two versions is confusing. A PSR needs to be a simple and clear
message: one solution, one version, one recommended way to do it.
It's also (IMO) a good thing that the FIG pushes PHP 7 forward.
Mat
>
> Something like that is pretty stupid. It prevents having an implementation
>> that's compatible with both, 5.6 and 7. And two versions of a package can't
>> be installed side-by-side with Composer. New major versions of PSRs should
>> definitely use new package names for that reason.
>>
>>
On Fri, Aug 4, 2017 at 7:16 AM, Niklas Keller
wrote:
> On Friday, August 4, 2017 at 10:54:08 AM UTC+2, Adrien Crivelli wrote:
>>
>> I can see that Woody is feeling strongly in favor of support of PHP 5.6.
>> I assume he knows what he is talking about better than myself and will
>> trust him on th
Il giorno ven 4 ago 2017 alle ore 14:16 Niklas Keller <
nicks.post.kes...@gmail.com> ha scritto:
> Something like that is pretty stupid. It prevents having an implementation
> that's compatible with both, 5.6 and 7. And two versions of a package can't
> be installed side-by-side with Composer. New
On Friday, August 4, 2017 at 10:54:08 AM UTC+2, Adrien Crivelli wrote:
>
> I can see that Woody is feeling strongly in favor of support of PHP 5.6. I
> assume he knows what he is talking about better than myself and will trust
> him on that. Let's not waste more time debating on something that ca
On Friday, August 4, 2017 at 10:54:08 AM UTC+2, Adrien Crivelli wrote:
>
> I can see that Woody is feeling strongly in favor of support of PHP 5.6. I
> assume he knows what he is talking about better than myself and will trust
> him on that. Let's not waste more time debating on something that ca
I can see that Woody is feeling strongly in favor of support of PHP 5.6. I
assume he knows what he is talking about better than myself and will trust
him on that. Let's not waste more time debating on something that can be
implemented quickly and easily (with a 1.0 for PHP 5.6 and 2.0 for PHP 7+
I think the real problem behind this discussion is PSR versioning. We
should address that first, because the process of releasing a new PSR to
bump requirements is time consuming and inefficient, as Woody maybe wrote
between the lines.
Il Gio 3 Ago 2017, 18:26 Woody Gilk ha scritto:
> On Thu, Au
On Thu, Aug 3, 2017 at 10:37 AM, Larry Garfield
wrote:
> Let's go ahead and target PHP 7.0 for PSR-15 outright.
>
I'm going to say no to this. There is already a significant ecosystem of
middleware that supports PHP 5.6 and I want those early adopters to be able
to use PSR-15 right away. It will
The question, I think, is how far ahead should we look? For example, if we
decide to target PHP 7, but not 7.1, that will be EOL’d in a year and four
months. PSR-15 has been in limbo for nearly that long…!
PHP 7.1 will be EOL’d in two years and four months — that’s coming faster than
you’d thin
On 08/03/2017 07:17 AM, Adrien Crivelli wrote:
>
> On Wednesday, 2 August 2017 19:01:34 UTC+2, Woody Gilk wrote:
>
> > This would require >= PHP 7
>
> That's a non-starter. There are plenty of people stuck on PHP 5.x
> for various reasons and I don't want to shut them out.
>
>
> PHP 7+
11 matches
Mail list logo
