Roadmaps for 4.0.0 and 5.0.0

[bradynpoulsen]

I'd be interested in helping to stabilize the v4 code APIs. Do you have a roadmap on what is still needing to be completed?

[jansor]

Hi, just curious, is their any timeline when this would be released?

[mtyeh411]

on a similar note, how would we grade the stability of current latest (4.0-alpha)? should it not be considered production-ready? if so, what is work is outstanding to reach stable/production-ready?

[lcobucci]

Hey folks, sorry for the delayed response (I was on family vacations 😄).

The plan for v4.0 is essentially this:

• Finish the work started in Remove inline signaling from Key #339 (comment) (which would allow us to do Support JWK #32 without breaking BC)
• Implement Use library specific exceptions #128
• Require PHP 7.4
• Backport changes to v3.x in a BC-compatible manner to create a migration path

The first 2 items are the ones which would modify the API, apart from that everything is pretty much stable. Although I do use the alpha version in production, I'd suggest you wait until those items are done to avoid having to modify things on your apps (or you use it knowing that things will change).

I don't have a timeline (sorry) but my hope is to tackle these things in the upcoming months (after I release a new version of @chimeraphp packages).

[GrahamCampbell]

Require PHP 7.4

Which features are you looking to use from PHP 7.4?

[Ocramius]

Just bumping the min version to current stable is sufficient 👍

Besides that, typed properties, obviously

[ZhangChengLin]

Are you planning to change from the BSD 3 license to the MIT license after version 4?
@lcobucci

[lcobucci]

@ZhangChengLin we can surely change, AFAIK BSD-3 is as permissive as MIT so I didn't bother to change back then. However, I'm not an expert in that area and if that's an issue for you I can definitely modify it.

[ZhangChengLin]

@ZhangChengLin we can surely change, AFAIK BSD-3 is as permissive as MIT so I didn't bother to change back then. However, I'm not an expert in that area and if that's an issue for you I can definitely modify it.

I do n’t know much about this either. I just see that many projects are using the MIT license, so I feel that if they are the same, then maybe you can introduce more about the idea of ​​using this license in the readme.5.5k star, Someone can give you the answer you want.

I think that the current license has no effect on me.

[Ocramius]

BSD/MIT are pretty much the same: changing license is much more effort (need to hunt down all previous contributors and ask for their opinion)

…

On Sat, May 30, 2020, 20:52 张成林 ***@***.***> wrote: @ZhangChengLin <https://github.com/zhangchenglin> we can surely change, AFAIK BSD-3 is as permissive as MIT so I didn't bother to change back then. However, I'm not an expert in that area and if that's an issue for you I can definitely modify it. I do n’t know much about this either. I just see that many projects are using the MIT license, so I feel that if they are the same, then maybe you can introduce more about the idea of ​​using this license in the readme. Someone can give you the answer you want. I think that the current license has no effect on me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#300 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFVEGAQ3URYPEPU3DDK33RUFIXZANCNFSM4HYZ36JQ> .

[GrahamCampbell]

RE PHP version stats from composer, only 1 in 5 people are using PHP 7.4. PHP 7.2 is still the most popular version...

[ZhangChengLin]

BSD/MIT are pretty much the same: changing license is much more effort (need to hunt down all previous contributors and ask for their opinion)

I don't understand this, so it's so troublesome?

[Ocramius]

Yes, **changing** license is a lot of work

…

On Sat, May 30, 2020, 21:58 张成林 ***@***.***> wrote: BSD/MIT are pretty much the same: changing license is much more effort (need to hunt down all previous contributors and ask for their opinion) I don't understand this, so it's so troublesome? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#300 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFVEECWHQCUKZEE4Q3JPDRUFQPJANCNFSM4HYZ36JQ> .

[GrahamCampbell]

Besides that, typed properties, obviously

It all your properties are private, typing them in the language is only gonna give you a slowdown at runtime for no benefits, compared to using a static analyzer and phpdoc?

[Ocramius]

It will add runtime invariants, should any initialisation escape our analysis.

In general, the overhead is negligible, compared to the advantages: if you are worried about this kind of overhead, you can write a plugin to drop all typed properties post installation.

[Ocramius]

Besides, adding types explicitly can aid compilers and reflectors 👍