Sounds like a documentation issue. Could I use this as my first contribution?
Could you help me gest started?: https://github.com/FriendsOfSymfony/FOSRestBundle/issues/384#issuecomment-14428222 On Monday, March 4, 2013 10:10:55 PM UTC+1, Lukas Kahwe Smith wrote: > > > On 04.03.2013, at 19:06, Johannes Schmitt <[email protected]<javascript:>> > wrote: > > Personally, I think instead of having each bundle author relax constraints > and/or delay releases, how about educating users to use in their root > package something like: > > require: { > "symfony/symfony": "2.3-dev as 2.2" > } > > 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? > > > i agree. this looks much better and makes the tagging of new releases much > safer. > > regards, > Lukas > > -- -- 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.
