Skip to content
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

[TASK] Drop support for PHP < 5.6 #136

Closed
wants to merge 1 commit into from
Closed

[TASK] Drop support for PHP < 5.6 #136

wants to merge 1 commit into from

Conversation

oliverklee
Copy link
Contributor

@oliverklee oliverklee commented Jan 31, 2017

PHP 5.4 and PHP 5.5 have reached their end of life and thus are not
supported anymore (not even with security updates). So PHPList will
not support it anymore, either.

This will also fix the Travis build which has been broken for PHP 5.3.

PHP 5.3, 5.4 and PHP 5.5 have reached their end of life and thus are not
supported anymore (not even with security updates). So PHPList will
not support it anymore, either.

This will also fix the Travis build which has been broken for PHP 5.3.
@michield
Copy link
Member

  1. we discussed this on the list, and for now decided to keep 5.4 and up for a while
  2. changes to PHPMailer should be contributed to the PHPMailer project.

@michield michield closed this Jan 31, 2017
@michield
Copy link
Member

By the way, the travis build will resolve once I merge dev33 into master, which will be soon.

@oliverklee
Copy link
Contributor Author

@michield So it would be okay to at least drop support for 5.3? Then I'll create a PR for that.

@oliverklee
Copy link
Contributor Author

@michield And would it make sense to include PHPMailer via composer? Then PhpList could always have the latest version.

@michield
Copy link
Member

I guess we can drop 5.3. The main reason I kept it for now, is that it only fails on some unused files in PHPMailer, so basically phpList still is fine with 5.3

PHPMailer via composer is a nice idea. Currently we only use composer for the CI stuff.

@oliverklee
Copy link
Contributor Author

oliverklee commented Jan 31, 2017

Okay, then I'll take care of that. I've created issues #137, #138 and #139 for this. @michield Thanks for the quick feedback!

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

Successfully merging this pull request may close these issues.

None yet

2 participants