Ok, so he was talking about current development process not about breaking compatibility after release.
2011/3/6 Thor <thorste...@gmail.com>: > he was talking about updates in symfony 2.0.0 , since it's not yet > released. > They also told that the last backward-compatibility break has been > made 15 days ago. > For what i understood, the problem is that since it's not either a > release candidate yet, so you could download a so called > "distribution" that with the next update will not work. > > It's still being developed. > > On 6 Mar, 12:16, Michał Piotrowski <mkkp...@gmail.com> wrote: >> 2011/3/6 Thor <thorste...@gmail.com>: >> >> > what fabien himself said is that it's really possible that further >> > updates on the sf2 distributions could break backward compatibility. >> >> About what updates he was talking? Did he meant 2.0.x updates or 2.x >> updates? When it comes to the first, I would rather advocate to delay >> Symfony2 release. From my POV Symfony2 should be released when it's >> ready. >> >> > So if you're going to plan a big system, the lifespan of the system >> > becomes a very important variable: >> > i guess it has to live more than a couple of years, so, starting with >> > a stable framework could make the difference when they'll release >> > bugfixes and optimizations. >> >> > I really don't know if sf2 is still the best choice for a big >> > production project. >> > It has been said anyway that's enough stable to test it, build >> > something that works (that will probably not have its framework >> > updated) and make experience with it so... >> >> > On 3 Mar, 19:44, Gustavo Adrian <comfortablynum...@gmail.com> wrote: >> >> Actually there're a lot of Bundles and Doctrine extensions now (including >> >> a >> >> nested set implementation). Everyone has a different opinion on this >> >> matter. >> >> I'm using Symfony 2 for my CRM and I must say it's the best choice I >> >> made. I >> >> need the flexibility it gives you. >> >> >> Anyway, the only way to know is to give both a try. >> >> >> On Thu, Mar 3, 2011 at 3:22 PM, Thor <thorste...@gmail.com> wrote: >> >> > i don't agree with everything: >> >> > actually some plugin gives a good starting point for some kind of >> >> > solutions; >> >> >> > for example if i needed a nested set for something i probably wouldn't >> >> > start from scratch; >> >> >> > anyway, i think that the plugin question is purely project-dependant: >> >> > what i meant with >> >> >> > "i'd think IF i needed that" was just that: if someone doesn't needed >> >> > plugins sf2 could be a good starting point. >> >> >> > btw today at sflive fabien said it's not. >> >> >> > On 1 Mar, 17:53, Michał Piotrowski <mkkp...@gmail.com> wrote: >> >> > > 2011/3/1 Thor <thorste...@gmail.com>: >> >> >> > > > Are all sf 1.4 plugins already available in 2.0? >> >> >> > > Do you really need all sf 1.4 plugins? :) >> >> >> > > > if not, i'd think if i needed that >> >> >> > > For a large project you most likely want to write almost everything by >> >> > yourself. >> >> >> > > Back to the topic. In December I started a large project and I decided >> >> > > that I will use symfony 1.4. I do not regret that decision. If I chose >> >> > > Symfony2 then, I wouldn't have so many working code now. What has >> >> > > changed over the past three months? >> >> > > - Symfony2 is now more polished >> >> > > - in a few days there will be a version with stable API >> >> > > - documentation increasingly growing >> >> > > - more and more Bundles, code snippets >> >> >> > > From my POV Symfony2 now is very worth considering if you don't have >> >> > > any "ASAP deadline" for project. >> >> >> > > -- >> >> > > Best regards, >> >> > > Michal >> >> >> > >http://eventhorizon.pl/ >> >> >> > -- >> >> > 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 users" group. >> >> > To post to this group, send email to symfony-users@googlegroups.com >> >> > To unsubscribe from this group, send email to >> >> > symfony-users+unsubscr...@googlegroups.com >> >> > For more options, visit this group at >> >> >http://groups.google.com/group/symfony-users?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 users" group. >> > To post to this group, send email to symfony-users@googlegroups.com >> > To unsubscribe from this group, send email to >> > symfony-users+unsubscr...@googlegroups.com >> > For more options, visit this group at >> >http://groups.google.com/group/symfony-users?hl=en >> >> -- >> Best regards, >> Michal >> >> http://eventhorizon.pl/ > > -- > 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 users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- Best regards, Michal http://eventhorizon.pl/ -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
