Le 05/03/2013 13:36, Lukas Smith a écrit :
On Mar 5, 2013, at 11:37 , Jordi Boggiano <[email protected]> wrote:
Heya,
As you can see we are currently using ">=2.0,<2.3-dev" here, which
probably needs to be bumped to ">=2.0,<2.4-dev" now that 2.2 is
out. Obviously its possible for BC breaks during the development of
2.3, as such I guess we need to avoid tagging a stable release
with ">=2.0,<2.4-dev" until 2.3 is released as stable.
Indeed tagging with a <2.4-dev requirement before 2.3 is released is
not so great. Then again I'd hope we can more and more rely on ~2.0
and similar, as BC breaks become more rare.
so you agree that until then "symfony/symfony": "2.3-dev as 2.2" is the right
approach?
if so, does someone have time to work on a cookbook entry for this?
(maybe this blog post can help a bit
https://igor.io/2013/01/07/composer-versioning.html)
there is a big drawback with this approach: if a bundle created a new
version targetting 2.3 (because of changes in Symfony for which they
need to adjust), you would still install the version for 2.2 as Composer
will use "symfony/symfony 2.2" as version when resolving deps.
--
Christophe | Stof
--
--
If you want to report a vulnerability issue on Symfony, please read the
procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
---
You received this message because you are subscribed to the Google Groups "Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
