Aloha, I just wanted to check in regard the best strategy for specifying dependencies and how to manage dev-master dependencies related to the dev-master symfony/symfony repo.
Here is an example of FOSRest which depends on HttpFoundation which is supposed to be stable, as such we are using "~2.0" which effectively means "any version since 2.0 that is below 3.0": https://github.com/FriendsOfSymfony/FOSRest/blob/master/composer.json Now for FOSRestBundle we have several dependencies which are not yet stable. As such its a bigger question what to depend on in dev-master and inside releases: https://github.com/FriendsOfSymfony/FOSRestBundle/blob/master/composer.json 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. Am I correct so far? Any other recommendations concerns? Should we have this information inside a cookbook entry under the Bundle section? regards, Lukas Kahwe Smith sm...@pooteeweet.org
signature.asc
Description: Message signed with OpenPGP using GPGMail
