I hate to say it, because it means a lot of work for me too, but BC kills innovation. As Symfony 2 already introduce some new (core) concepts, it shouldn't change the course because of BC. I mean, it'll be a difficult migration from symfony 1 anyway.
Oh, and i didn't mentioned Doctrine 2 :o) Michael On 23 Feb., 09:19, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 2/23/10 7:40 AM, Gareth McCumskey wrote: > > > Hi Fabien, > > > Thanks for the response, its really appreciated. And its good to know > > that this will at least be looked at :). I do understand that not > > everything will be automated,but just as a baseline, with no > > automation, our current symfony 1.x project would take probably on the > > order of 6-8 months to transfer to Symfony 2.0 when its released and > > based on what I saw in that (exciting) presentation. > > > I guess thats partly why many frameworks do not end up doing a > > "rewrite" like this for their frameworks, because of backward > > compatability issues. > > That's also why some frameworks die. The web evolves fast. We need to > keep up with best practices. Unfortunately, the symfony 1 core > architecture was not flexible enough. That's also because frameworks in > PHP are quite young. So, we are still "experimenting" a lot of different > approaches. > > Fabien > > > > > > > On Mon, Feb 22, 2010 at 2:47 PM, Fabien Potencier > > <fabien.potenc...@symfony-project.com> wrote: > > >> On 2/22/10 11:53 AM, Gareth McCumskey wrote: > > >>> Hey all, > > >>> I just finished watching the presentation by Fabien about Symfony 2.0, > >>> and it really looks great. You can see that the lessons learnt > >>> developing symfony 1.x have paid off for this next major version. But > >>> I had a couple of questions... > > >>> Will Symfony 2.0 have some kind of upgrade capability for symfony 1.x > >>> projects? I don't necessarily mean total ease of upgrade, as I > >>> understand that its a totally different core etc, but, using us as an > >>> example, we have a very complex application that has taken a very long > >>> time to develop and even with LTS being to 2012, re-writing our entire > >>> app for Symfony 2.0 from scratch (or even semi-from scratch) would be > >>> a task that would take too long to contemplate. > > >>> If Symfony 2.0 will not have some kind of upgrade mechanism, will the > >>> symfony 1.x branch (?) have longer term support just for bug-fixes > >>> simply to allow people more time to make the transition? > > >> We are too early in the development of Symfony 2 to have a definitive > >> answer > >> to this question. We will do our best to ease the transition from symfony 1 > >> to Symfony 2, that's all I can say for now. But, as you have already > >> noticed, a lot of things are quite different, so we won't be able to > >> automate everything. > > >> Fabien > > >>> This is not in anyway a demand or ridicule simply just a request for > >>> information so we can long-term plan our releases a bit for our > >>> application. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "symfony users" group. > >> To post to this group, send email to symfony-us...@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. -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@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.
