Composer requirements for dev-master about doctrinebundle

[stof]

I'm still expecting to have the Symfony 2.1 release before the 2.3 release of Doctrine (which will occur in end June). So we cannot bump the requirement to higher versions as they will not be released at the time we will tag the bundle. (A requirement on a dev branch makes it impossible to tag as dev versions will change after that, especially master)

If Jackalope is not compatible with Doctrine 2.2, it will make things difficult for people using Symfony 2.1 once released, especially once Composer tries to enforce stable packages instead of defaulting to dev versions (which are higher) as currently.

[stof]

And I don't want to maintain 2 branches before the first release of the bundle. It makes things a pain as people are likely to contribute to master, requiring to redo all PRs and then to merge branches together where the only difference is the composer.json file

[bmatzner]

I get that. Need to get back in touch with Lukas then, asking him whether he'd be willing to make the changes there, which seems difficult because of jackalope/jackalope-doctrine-dbal#24 and composer/composer#614
Looks a bit like the hen and egg problem, and I'm afraid I'm not the person who could be of any help resolving this...

[stof]

closing this one as DoctrineBundle now allows both 2.2.* and 2.3.* for doctrine (and the master branch is aliased to 2.3.x-dev)