The 1.2 - 1.3 - 1.4 upgrade path isn't very difficult. 1.4 is just 1.2 with a lot of problems fixed and the 1.0 compatibility cruft removed. 1.3 is that plus the compatibility stuff. You should really look into following that path. We had little trouble migrating from 1.2 to 1.4 and all of the changes we had to make were improvements.
I have seen a few fixes for critical security bugs released for 1.2 by the Symfony team. On Wed, Jul 14, 2010 at 5:54 PM, Sid Bachtiar <[email protected]> wrote: > I do mean 1.2! I have a project still using 1.2+Propel! > > I know the "end-of-life" for 1.2 was last year, but the community can > still maintain it right? > > Not everyone can afford keeping up with the latest you know :) > > And although not as fancy as 2.0, 1.2 is not broken > > On Thu, Jul 15, 2010 at 9:52 AM, Tom Boutell <[email protected]> wrote: >> Sid, do you really mean 1.2? 1.2 was end-of-lifed last year. Do you >> mean Symfony 2.0? >> >> On Wed, Jul 14, 2010 at 5:50 PM, Sid Bachtiar <[email protected]> wrote: >>> Hi, >>> >>> How do I contribute to symfony 1.2? >>> >>> At the moment I just have something small to add >>> >>> I want to change: >>> >>> $this->addMessage('csrf_attack', 'CSRF attack detected.'); >>> >>> to: >>> >>> $this->addMessage('csrf_attack', >>> sfConfig::get('app_message_csrf_attack', 'CSRF attack detected.')); >>> >>> In sfValidatorCSRFToken.class.php so that I can customize the csrf >>> attack message without changing the core. >>> >>> >>> Regards, >>> >>> Sid >>> -- >>> Blue Horn Ltd - System Development >>> http://bluehorn.co.nz >>> >>> -- >>> 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 >> > > > > -- > Blue Horn Ltd - System Development > http://bluehorn.co.nz > > -- > 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
