Allow symfony 3.0 components

[nicolas-grekas]

Tests should tell if any deprecated interfaces of Symfony are used. If not, then the bundle is defacto compatible with 3.0

[doctrinebot]

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DDC-3584

We use Jira to track the state of pull requests and the versions they got
included in.

[nicolas-grekas]

Please note that symfony can not be properly tested until this one is merged

[nicolas-grekas]

ping @Ocramius
we must tweak our composer.json file in order to test Symfony 3.0 properly right now

[Ocramius]

We can't ensure compat with symfony 3.0 until it gets to RC state (frozen).
We already had enough trouble by allowing symfony 2.7 :(
On Aug 2, 2015 11:54, "Nicolas Grekas" [email protected] wrote:

ping @Ocramius https://github.com/Ocramius
we must tweak our composer.json file in order to test Symfony 3.0 properly
right now

—
Reply to this email directly or view it on GitHub
#1310 (comment).

[stof]

@Ocramius the Console component should be quite safe. There are no big BC breaks planned in it (the BC break is adding new methods in the OutputInterface, and this does not impact Doctrine as it does not re-implement its own output class)

[nicolas-grekas]

See symfony/symfony#15432

[Ocramius]

@stof I'll let semver decide that once there is a tagged BC-frozen version.
Poke back when at RC stage, right now I don't feel like upgrading and then chasing ghosts :-\

Yes, this is chicken and egg, but users can still have the root composer.json patched for the beta/RC stages.

[nicolas-grekas]

ping @Ocramius we can't seriously tag 3.0 without merging symfony/symfony#15432 but this PR blocks Same for doctrine/DoctrineCacheBundle#48

[Ocramius]

@nicolas-grekas shouldn't there be an RC or beta? Any ref to current stability? That said, can possibly tag tonight, but only the ORM (bundle not up to me)

[stof]

@Ocramius there will be beta. but we need to stop faking versions before tagging a beta release

[Ocramius]

Alright
On Nov 3, 2015 15:09, "Christophe Coevoet" [email protected] wrote:

@Ocramius https://github.com/Ocramius there will be beta. but we need
to stop faking versions before tagging a beta release

—
Reply to this email directly or view it on GitHub
#1310 (comment).

[stof]

@Ocramius note that I'm not asking you to tag a stable Doctrine version allowing Symfony 3 before the Symfony 3 RC releasese are there. Having a dev or beta version of doctrine during the beta releases of Symfony 3 is OK (and it allows you to polish the compat, even though it should be OK)

[Ocramius]

@nicolas-grekas now in 2.6.x-dev :-)

[nicolas-grekas]

Thanks ! What's the planned date for 2.6 to be tagged?