Open peter279k opened 4 years ago
This would require a major version bump (I am not opposed to this, just saying it will :)).
opposed
Hi @vlucas, thanks for your reply. I agree that it's a version bump.
Maybe we can consider releasing 2.0
version to resolve this issue?
I think that would be a necessity for dropping support of previously supported PHP versions, yes.
Not that anybody gives a shit, but I just chanced upon this framework and it's going to come in ideal for a project that needs to run on an internal legacy system where the PHP version cannot be changed for whatever reason. So it's kinda nice that this exists. Just sayin.
Not that anybody gives a shit, but I just chanced upon this framework and it's going to come in ideal for a project that needs to run on an internal legacy system where the PHP version cannot be changed for whatever reason. So it's kinda nice that this exists. Just sayin.
According to PHP's supported version: https://www.php.net/supported-versions.php Anything below version 7.3 is end of life (as of this post). Meaning there is a security risk in using them. But for those who don't care about such things, (due to internal systems etc), I suggest tagging a legacy compatible release. If your PHP version is years old, then you might not mind using old code (that is supported).
I think this repo should primarily stay in line with PHP's officially supported versions, that way we can benefit from the improvements of PHP, and we don't encourage users to use software that is no longer supported.
Since the
php-5.6
andphp-7.0
versions are inactive for official PHP team.And I think it's time to drop these above PHP versions and let this framework require
php-7.1
version at least.Once this issue is accepted, I'll happy to work on this :).