Drop support for PHP 5.6?

[ThomasLandauer]

Wouldn't you say it's about time to drop support for PHP 5.6 and go for 7.2+? https://github.com/Codeception/Codeception/blob/4.1/composer.json#L18
It has reached end-of-line almost 2 years ago: https://www.php.net/supported-versions.php

Just noticed this when looking at Codeception/module-rest#24 ...

[Naktibalda]

Fine with me if it happens in Codeception 5.

[ThomasLandauer]

There is no 5.0 branch yet - could you create one?

[Naktibalda]

Dropping support for PHP 5.6 is not a big enough feature to mandate release of a new major version.

[ThomasLandauer]

I didn't mean to release it. What's your plan to collect all changes targeted v5?

[SamMousa]

In my opinion, it makes more sense to drop support for all but the most recent version when we decide to do Codeception 5.

Personally I'd wait for a PHP8 stable release, then start a Codeception 5 branch that targets just PHP8 +.

[Naktibalda]

I would wait for PHPUnit 10 and support only it.

[Naktibalda]

As I wrote, it will happen in Codeception 5: #6064

[ThomasLandauer]

OK, great!
Is there a way to close this discussion?

[TavoNiievez]

Hey,
There is little more than 3 months of support for PHP 7.3, surely it will be much less when Codeception 5 is released. Do we still want that version to be compatible?

[c33s]

i work quite a lot with legacy projects. my personal opinion is to keep tools like testing frameworks, composer, rector,... as compatible as possible with old version. this is the only way to migrate a legacy 5.6 project to a higher php version.