We have just released Symfony2 PR12. It only contains small bug fixes and
enhancements, but also a major security fix which allowed all users to switch
to arbitrary accounts when the SwitchUserListener is activated
(configurations which do not use the SwitchUserListener are not affected).
This is the last preview release as the form branch will be merged just
after this release. As we will keep releasing one version per week, the first
beta release of Symfony2 will be published next week.
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.
This is the last preview release as the form branch will be merged just after this release. As we will keep releasing one version per week, the first beta release of Symfony2 will be published next week.
Can you please answer the questions about API freeze and documentation. I am choosing a framework for the project that starts late May. Is it safe to use symfony 2 at the of May?
All classes, methods, and properties tagged with @api are public in the sense that we guarantee their stability over time: their name, signature, and behavior won't change for any minor version of the library
@404, Thanks for your opinion. However the "Java concept" as you describe it is not the goal of Symfony. PHP as a language in recent years has started to adopt capabilities of other languages (Name spaces, and Closures for example) however none of these concepts is unique to Java. In fact comparing Symfony to Java is akin to comparing my cup of coffee to the Eiffel Tower. We who love Symfony wish you the best in your endeavors.
For those wondering what beta means:
" Entering beta means that all the main features of the framework will be available. That does not mean that we won't break backward compatibility here and there, but all these changes will be documented to ease migration."
I'm not sure if this feature is missing (I think it is), but could you please implement a logger feature for missing translations in the symfony translator?
That way the developers could work and put 'tokens' whenever translation is needed. Afterwards the translators would just peek in the logs and translate any entry that is missing from the catalogues.
I've got this error "Fatal error: Interface 'Symfony\Component\DependencyInjection\ParameterBag\ParameterBagInterface' not found in C:\wamp\www\Symfony\Symfony\vendor\symfony\src\Symfony\Component\DependencyInjection\ParameterBag\ParameterBag.php on line 19" the moment I ran WAMPSERVER. The earlier version worked fine. Is this the right forum for this sort of thing? Please advise.
Great news
Great news!
All classes, methods, and properties tagged with @api are public in the sense that we guarantee their stability over time: their name, signature, and behavior won't change for any minor version of the library
" Entering beta means that all the main features of the framework will be available. That does not mean that we won't break backward compatibility here and there, but all these changes will be documented to ease migration."
http://symfony.com/blog/symfony2-final-version-we-are-not-there-yet
Waiting more documentation...
That way the developers could work and put 'tokens' whenever translation is needed. Afterwards the translators would just peek in the logs and translate any entry that is missing from the catalogues.
Thanks in advance!