Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

PSR-15 progress tracker in Expressive modules #528

Closed
14 tasks done
michalbundyra opened this issue Nov 17, 2017 · 8 comments
Closed
14 tasks done

PSR-15 progress tracker in Expressive modules #528

michalbundyra opened this issue Nov 17, 2017 · 8 comments

Comments

@michalbundyra
Copy link
Member

michalbundyra commented Nov 17, 2017

Created issue here to track progress on updating expressive modules to support PSR-15.
It is not yet approved but in it is in the last phase and probably it will be approved and released in Jan 2018. If everything will be fine, the namespace will be only changed (and package name obv). Here is the list modules with associated PR with PSR-15 support which needs update. All (?) of these modules required major release, as this update is BC break. Minimum PHP requirement also is bumped to PHP 7.1 (in modules where it was PHP 5.6):

See also: https://discourse.zendframework.com/t/psr-15-compatibility-issues-and-proposal/378

@mano87
Copy link

mano87 commented Jan 30, 2018

Is there any news here?

@michalbundyra
Copy link
Member Author

@mano87 #543

@weierophinney
Copy link
Member

And, probably a better place to look is the Expressive v3 project in the zend-expressive-skeleton repository, as it tracks other related issues:

Right now, the time frame for final release is 4-6 weeks (end of February/mid-March).

@geerteltink
Copy link
Member

Closing this as all related PSR-15 PR's are merged.

@froschdesign
Copy link
Member

Next time: GitHub Project! 😃

@geerteltink
Copy link
Member

Or ask someone to create it for you: https://github.com/zendframework/zend-expressive-skeleton/projects/1

@michalbundyra
Copy link
Member Author

@froschdesign @xtreamwayz When I've created that "issue tracker" the project wasn't used in zend repositories (at least not in expressive) and many people didn't know if it is going ot be public. Don't blame now, please, for opening that issue :)

@weierophinney
Copy link
Member

@froschdesign At the time, I wasn't aware (and I'm not sure how many were) that projects on repositories are public, and that they can refer to issues/PRs in other repositories.

Now we know! So we can do things differently next time — and we actually have a few of these open now!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants