It does not make sense to work on an sf 1.5 version - for the reasons you mentioned: BC break is a no go. IMHO all "problems" can be solved by creating an appropriate plugin.
I really don't understand this 1.5 discussion. 1.4 is stable and has 3 years support and after a few months it already seems nobody wants to use it anymore.. Doctrine 1.2 also is stable so.. I would expect some nice projects on top of sf 1.4, for example a CMF (would make sense from business perspective) but instead people complain about sf 1.4 (again: it is stable) and wait for Symfony2 (will not be stable this year).. so.. I really don't get it.. regards, Matthias On 30 Aug., 17:38, Lukas Kahwe Smith <[email protected]> wrote: > On 30.08.2010, at 09:29, Stéphane wrote: > > > Any 1.5 so ? :-) > > > Shall we fork this ? > > > Any PoC on DI on forms on SF 1.4 ? > > What would it take to do so ? > > if there are _several_ worthwhile improvements on the table on top of 1.4, i > think we should consider a 1.5. in this case it wouldnt make sense however to > introduce the SF2 Di or form classes. for one they are 5.3 only .. but more > importantly it only makes sense to do a 1.5 if there are close to zero BC > breaks and essentially just feature additions. if there are a ton of BC > breaks in 1.5, then you might as well make the jump to symfony2. > > regards, > Lukas Kahwe Smith > [email protected] -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
