I was expecting to announce the first preview release today, but that won't be
the case. Instead, let's celebrate the latest beta version of Symfony 2.0,
beta5.
The good news is that we are almost there. So, the first release candidate
will be released at the end of next week. We will then have some more RCs
before the final release, which is expected to be released in July. The exact
date will depend on how many RCs will be needed to stabilize the current code
base.
This release comes with many enhancements and bug fixes, mostly for the
Doctrine bundle and the Form framework. As always, read the
UPDATE file
carefully to upgrade your applications.
If you are curious about what has changed, have a look at the
diff.
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.
I am really new about Symfony. and try to following step by step Book Docs.. but sometime got error massage.. I am not sure if Book Docs are up to date with new Symfony release..
I'm in the same situation that "Asiansexynine" but I think it's something obvious because the quick evolution and constant changes to the code (as long as the docs aren't being auto-generated from comments on the code).
@Asiansexynine: All we are excited and expecting the stable release but it's for sure that docs will be alway a bit behind the real code until it hist the Stable stage. Be patient (i'll try too)
for those who use superclass with doctrine 2. You need to dl the latest version of doctrine which includes this fix:
http://www.doctrine-project.org/jira/browse/DDC-1212
I noticed some changes in "Default Twig form templates". I know one can override default twig blocks(What I have done to resolve the problem) But I think one issue should be fixed. A "Read-Only" form field must not be rendered as "disabled" HTML attribute. Instead it should be rendered as "readonly". Because a disabled field's data does not appear in the $_POST, so you can not persist it. Consider a readonly text field which is filled by a javascript date picker, the user should not be able to type in the text filed, but it is filled by the date picker and you need the data when the form is posted. If you use a disabled form field you may not have access to the date filled filled by the picker.
Please update your current documentation to stay updated with all changes in Symfony2 beta releases so we can have a proper documentation as soon as the first RC are out.
Can't wait for the end of the week and for the FINAL release.
Keep up the good work.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
I am really new about Symfony. and try to following step by step Book Docs.. but sometime got error massage.. I am not sure if Book Docs are up to date with new Symfony release..
@Asiansexynine: All we are excited and expecting the stable release but it's for sure that docs will be alway a bit behind the real code until it hist the Stable stage. Be patient (i'll try too)
for those who use superclass with doctrine 2. You need to dl the latest version of doctrine which includes this fix:
http://www.doctrine-project.org/jira/browse/DDC-1212
It's not in Symfony2 beta5.
in /vendor/symfony/src/Symfony/Component/DependencyInjection/Compiler :
ResolveDefinitionTemplatesPass.ph
ResolveReferencesToAliasesPass.ph
/vendor/bundles/Symfony/Bundle/AsseticBundle/DependencyInjection/Compiler/CheckCssEmbedFilterPass.ph[p]
/vendor/symfony/src/Symfony/Component/DependencyInjection/Loader/schema/dic/services/services-1.0.xs[d]
/vendor/symfony/src/Symfony/Bundle/SecurityBundle/DependencyInjection/Security/Factory/HttpDigestFactory.ph[p]
/vendor/symfony/src/Symfony/Bundle/SecurityBundle/DependencyInjection/Security/Factory/RememberMeFactory.ph[p]
/vendor/bundles/Symfony/Bundle/WebConfiguratorBundle/DependencyInjection/SymfonyWebConfiguratorExtension.ph[p]
/vendor/symfony/src/Symfony/Component/Security/Core/Authentication/AuthenticationManagerInterface.ph[p]
My question would be: will you do another audit on the framework before it's final release? like you did back in January?
@Florin: We are going to schedule the security audit ASAP.
I can't wait to the stable version
Regards from Uruguay!
I'm also willing to help $$ -if needed - as I'm already making $$ with this amazing framework :D
Can't wait for the end of the week and for the FINAL release.
Keep up the good work.