-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
3.0
-
None
-
MOODLE_30_STABLE
I'm seeing mixed messages about whether we're intending to backport PHP7 fixes to stable branches or not.
I think we all can agree that PHP7 has a different sort of motivation than a usual php release, just look at the fact multiple of our partners have already posted marketing articles about it.
I would propose the following:
- We try to fix all compatibility issues with the most simple and straight forward fixes possible and discourage major refactoring simply for the goal of achieving PHP7 compatibility. The intent would be to backport to supported branches
- There might be some changes which developers/integrators do not deem as safe to make on stable branches - thats OK. There is still benefit in having all the rest of the simple fixes backported - partners (or HQ for our projects) might decide to take that risk and do those risky backports, and we might do it in a backporkport request later.
What I don't really want to see us doing is avoiding straight forward fixes because of policy or encouraging people to let loose with the refactoring which will make the solution to the problems take a different approach.
Please post the outcome of this on the general developer forum.
- blocks
-
MDL-50565 Prepare Moodle for PHP7
-
- Closed
-