Symfony blog posts for April 2009

In accordance with our security policy, we are releasing today symfony 1.2.6 to fix a security issue that has been spotted by the symfony core team.

Symfony core developers committed this week several fixes across all branches, including an important security fix. Meanwhile, plugins momentum continues with record-breaking 16 new plugins and more than 28 updated plugins in just seven days.

This week symfony routing subframework got some fixes and even more optimizations. The event dispatcher was published as a standalone symfony component. Plugin frenzy continued with more than 35 plugins updated.

Plugins focused all the attention during this week: symfony achieved the 500th plugin milestone, a new plugin voting mechanism was introduced and the list of the most popular plugins was published. Symfony community joined this celebration updating 28 plugins and publishing 12 new plugins.

Today, the symfony community celebrates the 500th plugin, published on the official symfony plugin repository. That's a great achievement.

This week, symfony project unveiled "symfony components", a set of standalone libraries and components ready to be used in any PHP project. In addition, symfony performance got a huge boost with improvements in cache manager and a new option for routing sub-framework.

In the context of this economic crisis, you may not feel like buying new hardware but instead pay attention on what is slowing down your existing servers. During one of these optimization sessions, I discovered that in addition to our own mess, every page handled by symfony's routing was spending a constant and disproportionate amount of CPU time to initialize.

An optimization committed to all branches of symfony earlier today may increase your application's performance by up to 50%! (No, this is not another April Fools post.)

The Symfony team is pleased to announce its latest contribution to the open source community, the Symfony Service Exploder.