A patch is simple enough, but how would we prove it is BC? On Wed, Sep 1, 2010 at 2:59 PM, Jonathan Wage <[email protected]> wrote: > Hi, > I think the motivation for any of the core developers to take the time to > implement these types of bloat convenience features is very low. You say it > is BC, but we can't guarantee that. We don't even have a patch yet, nothing > has been tested. No matter if you think something is BC or not, introducing > a new feature means we're introducing a new risk that has to be managed and > made sure that it will not cause any problems. Weighing the cost and hassle > of it against the actual benefit just doesn't seem worth it to me. Just my > opinion. I personally have absolutely no interest in implementing this > feature and maintaining it. > However, if someone were to provide a patch and prove that it is BC and push > it through, then it might be possible. But, I don't see any of us doing it > :) > - Jon > > On Tue, Aug 31, 2010 at 5:43 PM, Tom Boutell <[email protected]> wrote: >> >> I wouldn't bring up things like this if I didn't want to use Symfony >> 1.4 anymore. (: >> >> The suggestion I made is backwards compatible. >> >> Fixing the build task to make it easier to specify alternate form >> generators for Doctrine, and perhaps pulling the default choices from >> factories.yml, would also be backwards compatible. >> >> I'm happy with 1.4 and getting tremendous amounts of work done with >> it, but figured it couldn't hurt to make a suggestion, especially one >> that does not break other people's code. >> >> I agree that a 1.5 release doesn't make a lot of sense. >> >> On Tue, Aug 31, 2010 at 6:17 PM, Matthias Nothhaft >> <[email protected]> wrote: >> > 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 >> > >> >> >> >> -- >> Tom Boutell >> P'unk Avenue >> 215 755 1330 >> punkave.com >> window.punkave.com >> >> -- >> 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 > > > > -- > Jonathan H. Wage > http://www.twitter.com/jwage > > -- > 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 >
-- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- 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
