Home

This is the project for implementing support of PHP 7.2 in Magento 2.

Approach to Implementation

See Approach to Implementation for the requirements and restrictions of the implementation process.

See Issues Board for the list of issues ready for development or in development.

Feel free to add an issue to the list of issues if you know such ones. Those will be reviewed by the core team to confirm before being taken to work.

3rd-party dependency - the issue is caused by dependency on a 3rd-party library. For example, a library doesn't support PHP 7.2
backward-incompatible - the fix/implementation might be backward incompatible. Must be resolved before Magento 2.3 release
blocker - the issue blocks resolution of other issue(s). For example, the issue causes a fatal error, which terminates execution of the application and so blocks validation/fixing of other scenarios
deprecated - usages of functionality deprecated in PHP 7.2
investigation-needed - an investigation is needed. A clear solution is not known yet, the issue can't be taken into development
requires-ee-changes - requires changes in Magento EE being merged together with the CE fix. Example: update of composer.json in CE requires same changes being applied to composer.json in Magento EE

There are the following branches in the repository:

2.3-develop - target branch for the fixes
workarounds - this is a branch with quick-fixes/workarounds to bypass fatal errors and other blockers. The purpose of this branch is to uncover as many issues as possible not waiting for final fixes of blocking issues

There are two Docker based environments to choose from.

The first environment uses a shared directory between the host Magento repository (local box) and the container website (Docker). When you make changes to your local repository the changes are also made in the container. The downside is you might have a performance degradation due to the vast size of the Magento code base.

This repository is located here: https://github.com/giabmf11/php72-devbox-shared-local you have to copy your changes into the container in order to see the changes.

The second environment uses file syncronization instead of a shared file system. The performance is better but you have to manually copy your changes into the container in order to evaluate your code changes.

Status meeting: every Thursday at 10am CST (4pm UTC) https://magento.zoom.us/j/804681785

Slack channel: #feature-php-72. Send an email to [email protected] to join