Release Candidates for symfony 1.3 and 1.4!

November 17, 2009 · Published by Avatar of Kris Wallsmith Kris Wallsmith

On the heels of a fantastic BugHuntDay held over the weekend, the symfony core team is happy to announce the immediate availability of the first release candidates for versions 1.3 and 1.4.

For those of you not familiar with the release and maintenance schedules for versions 1.3 and 1.4, take a look at our earlier About symfony 1.3 and symfony 1.4 blog post.

These release candidates address a number of defects and add a few minor enhancements to the 1.3 and 1.4 branches.

Optimizations

A number of components have been further optimized for these releases. Most notable is the routing factory, which performs as much as 25% faster than just the previous 1.3 beta2 release, though your mileage may vary. The new project:optimize task also does more now, eliminating a number of filesystem reads when loading template helpers.

Widget Translations

The text used for the options in choice widgets is now passed through the widget translation mechanism. As a part of this enhancement a number of strings have been added to the translation catalogues for the Doctrine and Propel admin generators. If you've worked on translations in the past and have a few moments, please help by updating the translation strings added in this changeset.

Two More Weeks

The stable releases of both symfony 1.3 and 1.4 are scheduled to go out two weeks from now, with one more release candidate for each in the meantime. If you haven't done so yet, please take a moment to upgrade a project to symfony 1.3 or start a new one with symfony 1.4. Be sure to read through what's new, the upgrade tutorial and the list of what's been deprecated for more information on these two latest releases of symfony.

Published in #Releases

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

Comments

Avatar of Fabian Lange
Fabian Lange said on Nov 17, 2009
The 1.3 routing is now twice as fast as the 1.2 one and consumes only half the amount of memory. Profiling now indicates no bottleneck anymore. Please let me know your results :-)
Avatar of John Cleveley
John Cleveley said on Nov 17, 2009
Awesome! Good work guys.
Avatar of EmiV
EmiV said on Nov 17, 2009
Cool! I'm testing 1.3 routing over 1.2 routing.
Avatar of Annis
Annis said on Nov 17, 2009
Really cool, thank you!

@EmiV: Post back to the symfony-devs mailing list in the "Routing with 1.3" thread with your findings, please? :)
Avatar of Ariel Arjona
Ariel Arjona said on Nov 17, 2009
1.3 on php 5.3 is faaaaaaaaaast :)

Are there any plans to make a push to update popular plugins like sf(Doctrine)GuardPlugin in time for the releases?
Avatar of M
M said on Nov 17, 2009
@Ariel Arjona

"Are there any plans to make a push to update popular plugins like sf(Doctrine)GuardPlugin in time for the releases?"

I'm using sfDoctrineGuardPlugin 3.0.0 with sf 1.3 since beta1 without problems. It works just fine.
Avatar of Jim K
Jim K said on Nov 17, 2009
Where can we download 1.4? I can only find the 1.3 on the install page.
Avatar of Fabien
Fabien said on Nov 18, 2009
@Jim K: I have updated the installation page for 1.4:

http://www.symfony-project.org/installation/1_4
Avatar of Antik
Antik said on Nov 18, 2009
project:optimize frontend does not work

Class sfDoctrineAdminGenerator does not exist

strange error, i do not use any admin generated modules in frontend.
Avatar of dziobacz
dziobacz said on Nov 25, 2009
Fabien You should change routing. Now when we want to pass Doctrine object from view from form to action we mast change routing file and add routing for models. For me Symfony is better than ASP.NET MVC (not Web Forms) - but routing is one of the worst things in symfony - You can see ASP.NET MVC overwiew here:
http://www.asp.net/learn/mvc/tutorial-21-cs.aspx
And here is their routing:
http://www.asp.net/learn/mvc/tutorial-05-cs.aspx

In ASP.NET MVC I don't need change routing file to could pass ORM objects from form in view to action.
Avatar of Lawrence Krubner
Lawrence Krubner said on Nov 25, 2009
1.4 is the same as 1.3, but with deprecated features dropped, yes?

Is there a page that offers a complete, concise list of all the features that are deprecated in 1.3? I'd like to be able to glance at a single page and see if the lack of any features, dropped from 1.4, would break my sites if I upgraded.
Avatar of Kris
Kris said on Nov 26, 2009
@Lawrence Take a look at the "deprecated" link at the very end of the post.

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.