-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core] Drop php 5.6 and php 7.0 support #2224
Conversation
Removing from todo. Looks like long array syntax is introduced in php 5.4, while I was thinking it is introduced in 7.0 |
Php 7.0 introduced "??". So it would be good to force use it with lints. |
Soon, php 7.3 will not be getting anymore security updates[0]. In my opinion we should enforce a minimum of php 7.4 in order to avoid security problems alltogether. It also makes the life of developers easier when they can use more recent language features such as the |
Lets skip those new language features for now. |
Lets allow user to use EOL php on their risk. Offtopic: In my fulltime paid work (Odoo related consultation) some customers are still running ERPs on Python 2 (reached EOL on Jan 1, 2020) or EOL versions of Python 3. |
php 5.6 reached end of life on Dec 31, 2018
php 7.0 reached end of life on Jan 10, 2019
https://www.php.net/eol.php
Closes #863
Reason to drop support is use getenv() without "varname" parameter, that it ised in #2100
TODOs: