Deprecated function usages

[gharlan]

There are some deprecated (since SF 2.7) function usages which should be fixed.

Examples:

[gharlan]

Would it be ok to bump the symfony min version from 2.5 to 2.7? 2.5 is dead, and 2.6 is in "security fixes only" mode and will be dead from 01/2016.

The fixes would be simpler.

[havvg]

Is there any technical reason for the required changes (didn't have a look at them by now) to raise the dependency version?

I'm against it, as there are probably applications out there, which do not require 2.7. Which is fine, if they don't have needs for it. So if this bundle does not require 2.7, we are not in charge or responsibility to raise the dependency for any application using this bundle.

[angelk]

There are symfony 2.8, in witch forms do no work. There is symfony 3.0, witch can't be installed because of composer requirements.

[havvg]

I'm on the current move:

There is a new branch 1.5 which raises the dependency to Symfony 2.8, which is the current LTS. I gave it a lot of thoughts, and this step is fine, we commit on an LTS and this will be easier to support on a new branch, while leaving the old branches. The old ones will only receive an update on the incompatibility of their respective Symfony versions.

The second branch (not created yet) will be 1.6, which will be Symfony 3.0 compatible, but 2.8 incompatible.

[havvg]

The former Propel1 bridge of the symfony package has been merged. In case you are still up to it, the 1.5 branch is ready for the changes.

The distributed phpunit.xml.dist disables the deprecation errors, you have to change the error level.

[gharlan]

@havvg I forgot to mention in my initial post that I'm talking about the propel 2.x version. What should be the min symfony version for 2.x branch?

[havvg]

@gharlan I would suggest ^2.8|^3.0, being ready for upcoming 3.4 LTS.