Archives


Master Symfony2 fundamentals

Be trained by SensioLabs experts (2 to 6 day sessions -- French or English).
trainings.sensiolabs.com

Discover the SensioLabs Support

Access to the SensioLabs Competency Center for an exclusive and tailor-made support on Symfony
sensiolabs.com

Fabien Potencier
Symfony2: Beta5 available
by Fabien Potencier – June 16, 2011 – 25 comments

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.

Download Symfony2 beta5 now!

Comments RSS

  • gravatar
    #1 Asiansexynine said on the 2011/06/16 at 20:13
    Great news!

    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..
  • gravatar
    #2 Tomasz Kowalczyk said on the 2011/06/16 at 20:40
    Great work! I can't wait to put my hands on Symfony2 stable (I feel that I'll lose my patience and use RC just when in comes :)).
  • gravatar
    #3 Jose Ortega said on the 2011/06/16 at 20:45
    Thanks.....!
  • gravatar
    #4 Vazgen said on the 2011/06/16 at 20:51
    Great, let's have a look. Thanks
  • gravatar
    #5 Josh said on the 2011/06/16 at 20:58
    Good news! I'm just waiting for improved security events. Got my eye on the pull request for interactive login failures.
  • gravatar
    #6 DJ said on the 2011/06/16 at 21:41
    Great. looking forward to get hands on GA release..!
  • gravatar
    #7 Fernando Martin said on the 2011/06/16 at 21:50
    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)
  • gravatar
    #8 Lukas said on the 2011/06/16 at 21:55
    patience is good .. submitting tickets or even better yet PR's to fix the issues is awesome :)
  • gravatar
    #9 hamza said on the 2011/06/16 at 22:36
    nice!
  • gravatar
    #10 Nico said on the 2011/06/17 at 00:43
    Thank god you didn't release the first ***Preview Release***, it would be a BIG step backward =P
  • gravatar
    #11 Francois Constant said on the 2011/06/17 at 03:58
    Great,

    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.
  • gravatar
    #12 Sylvio said on the 2011/06/17 at 09:44
    Be careful, there is 2 files bad named in the .tgz package ; there extension are .ph instead of .php

    in /vendor/symfony/src/Symfony/Component/DependencyInjection/Compiler :
    ResolveDefinitionTemplatesPass.ph
    ResolveReferencesToAliasesPass.ph
  • gravatar
    #13 Sylvio said on the 2011/06/17 at 09:58
    Also there is the same problem with other files :

    /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]
  • gravatar
    #14 Florin said on the 2011/06/17 at 11:44
    Great news about a release ''schedule'.

    My question would be: will you do another audit on the framework before it's final release? like you did back in January?
  • gravatar
    #15 Fabien said on the 2011/06/17 at 12:02
    @Sylvio: The archives are correct. Why tool do you use to unpack the archive? Which OS?

    @Florin: We are going to schedule the security audit ASAP.
  • gravatar
    #16 kawelo said on the 2011/06/17 at 13:18
    Good news !
    I can't wait to the stable version
  • gravatar
    #17 shakir said on the 2011/06/17 at 14:05
    Just great news
  • gravatar
    #18 Nicolás said on the 2011/06/17 at 15:08
    Amazing!! thank you for the big work!!

    Regards from Uruguay!
  • gravatar
    #19 Florin said on the 2011/06/17 at 15:51
    @Fabien: That's great news. If it's going to be donation driven like in January then I'll chip in a bit :)
  • gravatar
    #20 Chris said on the 2011/06/17 at 17:14
    Great news! After this beta and the begin of the RC, the APIs are stable and will not change anymore?
  • gravatar
    #21 Jafehet Barrera said on the 2011/06/17 at 17:45
    Good news, perfect.
  • gravatar
    #22 Oscar B. said on the 2011/06/18 at 02:34
    Thanks for the big news. Hope you can improve the Test chapter in documentation. Also, improve Test functionality to support various login mechanism.

    I'm also willing to help $$ -if needed - as I'm already making $$ with this amazing framework :D
  • gravatar
    #23 Peyman said on the 2011/06/18 at 05:28
    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.
  • gravatar
    #24 chanzeng said on the 2011/06/18 at 20:03
    this is really big shit.
  • gravatar
    #25 Edgar said on the 2011/06/22 at 05:36
    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.