I think you'd have to strike up a conversation on symfony-users and see if other parties are interested in doing a community-supported fork of 1.2... as far as I know there are no resources being put to managing changes to 1.2 that aren't major security problems.
On Wed, Jul 14, 2010 at 6:02 PM, Sid Bachtiar <[email protected]> wrote: > Yes, upgrading the core codes might not be hard, but don't forget the plugins. > > This is a big project with a lot of intricate parts, it will be > upgraded when a budget is available :) > > On Thu, Jul 15, 2010 at 9:58 AM, Keri Henare > <[email protected]> wrote: >> The upgrade to 1.3 is pretty easy from 1.2 and that's still supported. >> >> Kind regards, >> Keri Henare >> --------------------------------------------------- >> Chief Technical Officer >> Pixel Fusion >> >> [e] [email protected] >> [w] pixelfusion.co.nz >> [m] (+64) 021 874 552 >> [p] (+64) 09 550 3084 >> >> PLEASE NOTE: I check my email 3 times per day and will respond at these >> intervals. For anything urgent please ring me. >> --------------------------------------------------- >> >> On 15/07/2010, at 9:54 AM, Sid Bachtiar 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 >> >> -- >> 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
