Closed gorghoa closed 4 years ago
@vincentchalamon, I agree with the objective.
The difference with #39 is that this PR does not imply major version change (no BC break), just fix a CI failure. #39 will imply a major version bump.
I just want to be able to merge #38 without @magarzon to suffer a build failure.
Removing PHP5 from the CI is not a BC break. I would better just remove PHP5 from the CI, but not from the composer.json
Nope, but #39 will require a php version >= 7.x (in composer.json), hence requiring a major version bump IMO
Removing PHP5 from the CI is not a BC break. I would better just remove PHP5 from the CI, but not from the composer.json
That’s the point. I want to tag a minor release version compatible with php5.6 and allowing symfony 5
Then, I want to tag a new major version requiring a more recent php version, dropping all unsupported php version.tests.
thanks :)
Travis’ builds are failing on php5, blocking some useful PR.
Allowing them to fail.