Remove EOL PHP 5.4 from .travis.yml and composer.json - Fixes #5862

[tPl0ch]

See #5862 for more info

[Ocramius]

We should change this to ^5.5 || ^7.0

[tPl0ch]

@Ocramius Done

[soullivaneuh]

@Ocramius 👍 for version support dropping, but this should be done on a new major IMHO.

Dropping PHP support is BC break for developers using this bundle under the dropped version.

[Ocramius]

Dropping PHP support is BC break

This has been discussed ad-nauseam. Dependency requirement bumps (any dependency) are not BC breaks. This will not break running systems, and systems running 5.4 will simply reject Doctrine ORM 2.6.x when running composer update, falling back to 2.5.x.

We've also done this previously in the 2.4 -> 2.5 upgrade.

should be done on a new major IMHO.

Done it multiple times in Doctrine, in Zendframework and in other libraries: not a problem, and also not perceived as a problem by consumers. Dropping support for un-maintained PHP versions is also the most responsible thing to do from a security perspective.

[Ocramius]

Failing tests are related to #5854 and #5856

[Ocramius]

Thanks, @tPl0ch!

[soullivaneuh]

@Ocramius I understand, you are technically right.

Symfony does not follows this way, so I think it's a matter of choices...

Thanks for your explanation anyway. 👍

[Ocramius]

Symfony does not follows this way, so I think it's a matter of choices...

Top of the page says doctrine/, in fact, not symfony/ :-P
Also, we don't have the throughput capabilities of Symfony: less versions to maintain is just less headaches.

[soullivaneuh]

Top of the page says doctrine/, in fact, not symfony/ :-P

Yeas I know, this is was I said:

so I think it's a matter of choices

😉

Also, we don't have the throughput capabilities of Symfony: less versions to maintain is just less headaches.

I totally understand you for this point. 👍 Having same issue for Sonata projects.

[tPl0ch]

@soullivaneuh In addition to @Ocramius points I also believe that libraries can be a vital driver for new PHP version adoptions this way. When an EOL is reached it's time to increase the pressure on consumers, and libraries like doctrine can instrument a big leverage here.