-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Future of the project: v1.23.8 / v1.24 / v2.0 #80
Comments
@cypherbits I personally think that this would be a waste of effort because all PHP versions older than 7.2 have already reached EOL and therefore do not receive security updates anymore. Even PHP 7.2 will only receive another three months of security updates before it reaches EOL as well: https://www.php.net/supported-versions.php |
I think moving to the newer versions of PHP would be a good idea but maybe have a branch or explain how to patch that version sometimes people are locked in to the versions of php and platforms there using so it's not about people been unsafe willingly even tho there are a few, I myself would create a wiki page on how to patch it, so the ones who want to do the work can, but once you put that much time in might be easier with a branch already does it lol |
What do you think about this @DanWin ? |
After merging pull requests #75 and #76 and #77 and fixing issue #72 we should release 1.24 as a non-backward compatible release.
We should remake everything for version 2.0
Question: Should we release a bug-vulnerability-fixing version v1.23.8 for people not wanting to upgrade PHP to at least 7.2??
The text was updated successfully, but these errors were encountered: