Heya, >> 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? > > Correct .. it would always require a new release to "tag" code as being > compatible with a newer version (though of course with the 2.3 as 2.2 it can > always be forced from the outside). > > Since FOSRestBundle as of now works with 2.0, 2.1 and 2.2 the symfony version > requirement should be ">=2.0,<2.3-dev" with this approach. Meaning that it > would not be marked compatible with dev-master of symfony.
I think this is actually a big deal. For high profile bundles like FOSRestBundle/FOSUserBundle, maybe playing it safe is best, but I would not recommend making this the best practice, because in most cases after 2.3 there shouldn't be major BC breaks anymore, so most bundles that have a low contact surface with the framework can expect to just work. For those I would recommend a ~2.1 or such requirement, because typically they will be less actively maintained and having a new tag to support the new symfony version will take weeks/months. If we have to go through this every six months it sucks. Also note that by default, even if you say ~2.1, composer won't use symfony 2.3 atm since there is no stable release of it. The root package also defines stability requirements so everyone is in control of which version they want to use. Now of course if a BC break appears in the 2.3.0 release then yeah people will upgrade and suffer bugs. That's why we should strive to avoid those and follow semver.org as strictly as possible. Cheers -- Jordi Boggiano @seldaek - http://nelm.io/jordi -- -- 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.
