On Thursday, March 7, 2013 2:15:37 AM UTC-6, Marco Pivetta wrote: > @Beau: that's common practice for users who want to stay bleeding edge. It > basically requires 2.3-dev and still lets other required packages "see" it > as 2.2 (compatible). >
I see. I maybe saw someone talk mention this once or twice but I've never really seen it in action. Thanks for the clarification. :) How does it impact Lukas's original question? Would a package like FOSRestBundle then be updated to something like ">=2.0,<2.2-dev" and then someone could opt into say, "2.3-dev as 2.2" or "2.4-dev as 2.2?" This would still mean that a tagged FOSRestBundle won't work for 2.3 or 2.4, even if it turns out there are no BC breaks, right? Maybe that is better than a tagged version that says it works with something that it doesn't? -- -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com 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 symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
