Yep, totally agree with tagging, but using the 2.0.x naming wouldn't let bundles communicate a BC-breaking release number properly (and I would like to see transparency in the bundle docs about BC breaks, now that we're stable). But, if we don't follow the 2.0.x naming, then we should at least be consistent and verbose about the Sf2 version compatibility somehow.
Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Thu, Jul 28, 2011 at 8:14 AM, Christophe COEVOET <s...@notk.org> wrote: > Le 28/07/2011 15:00, beberlei a écrit : > > Hello everyone, >> >> the 2.0 release being out now i would like to encourage every bundle >> author to verify that their bundles work with the current version and tag >> the bundles then. I suggest a version schemeing of "2.0.0", i.e. marking the >> bundle to work with 2.0.x of Symfony, and the third number is the version of >> the bundle. Other ideas are welcome. >> >> I will begin tagging the Bundles that I worked on this evening. >> > I don't think we should use the versionning of Symfony for the bundles. > They will have different release cycles so I find it more logical not to > impose such a restriction for the bundle version. > It would also introduce issues for the next Sf2 releases: what about a > bundle that deal with a stable component and may not require any change for > 2.1 ? Will it need to release a version 2.1.0 just to mark it is compatible > with 2.1 (whereas it is in fact entirely the same code) ? > > Beside that, I agree about tagging the bundles. I plan to release > FOSUserBundle in a few days as I want to include some pending todos in the > release. > > -- > Christophe | Stof > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > 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+unsubscribe@**googlegroups.com<symfony-devs%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/**group/symfony-devs?hl=en<http://groups.google.com/group/symfony-devs?hl=en> > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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