Blog

Comments

• 

  #1 Bart Guliker said on the 2011/04/19 at 13:06
  Does this mean that starting with the first bèta the features and API will be frozen and only bugs will be fixed? Or are there still planned changes?
• 

  #2 Amo__ said on the 2011/04/19 at 13:37
  <quote>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.</quote>
  
  Great news
• 

  #3 Stereoscott said on the 2011/04/19 at 13:53
  We appreciate all of the time and hard work the community has invested in this release.
• 

  #4 Brown agent said on the 2011/04/19 at 14:02
  the first beta release of Symfony2 will be published next week.--->
  Great news!
• 

  #5 shakir said on the 2011/04/19 at 14:29
  very godd news
• 

  #6 Amalgame said on the 2011/04/19 at 15:37
  \o/
• 

  #7 Maximiliano said on the 2011/04/19 at 18:29
  Does it means that the Symfony API will not be changed and only bugs will be fixed??
• 

  #8 nymo said on the 2011/04/19 at 20:20
  really great news! it's like an eastern present :)
• 

  #9 GreatGatsby said on the 2011/04/19 at 21:10
  Documentation: Will you begin publishing more documentation with the beta releases?
• 

  #10 Jonathan Nieto said on the 2011/04/19 at 22:06
  Thanks for your hard work guys!!!!! Looking forward the Symfony2 stable release!
• 

  #11 Juan Maia said on the 2011/04/19 at 22:15
  Great!!! Im looking forward to this!
• 

  #12 Ptheg said on the 2011/04/19 at 22:27
  Great news.
• 

  #13 Ilya Biryukov said on the 2011/04/19 at 23:50
  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?
• 

  #14 ScareCrow said on the 2011/04/20 at 08:32
  http://fabien.potencier.org/article/47/pragmatism-over-theory-protected-vs-private
  
  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
• 

  #15 Nico said on the 2011/04/20 at 09:25
  @Ilya : IMO, yes, because the form branch is actualy the blocking component, but he will be merged for next week in the first Beta
• 

  #16 Mauricio said on the 2011/04/20 at 09:54
  Very good news... thanks a lot for your hard work. I'm already working on a huge project that will be supported by Symfony2. :-)
• 

  #17 Cécil said on the 2011/04/20 at 10:25
  Very good news, (all) your work is appreciated very much!
• 

  #18 Jerome said on the 2011/04/20 at 12:47
  Great news! Looking forward to test this beta release! Thanks for your work.
• 

  #19 Maxime D said on the 2011/04/20 at 14:25
  Thank you very much for all this tremendous work. Looking forward to use it.
• 

  #20 404 said on the 2011/04/20 at 14:37
  You guys at symfony are a bunch of sad pathetic human beings , all you're doing is copying the Java concept to php.
• 

  #21 Greg Militello said on the 2011/04/20 at 19:44
  @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.
• 

  #22 M. said on the 2011/04/21 at 19:12
  Thank you for your work! this is indeed a very good news
• 

  #23 Seo für Google said on the 2011/04/21 at 19:42
  I like the symfony projects. These websites have very good performance.It is easy to optimize for search engines.
• 

  #24 Lukas said on the 2011/04/22 at 07:06
  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."
  
  http://symfony.com/blog/symfony2-final-version-we-are-not-there-yet
• 

  #25 Sergio Rus said on the 2011/04/22 at 10:08
  Congratulations! I'm currently using Symfony 1.4 for my projects, but I think I will move to Symfony2 soon. Well done!
• 

  #26 Enkuso said on the 2011/04/23 at 07:29
  Great news. Keep going hard work.
  
  Waiting more documentation...
• 

  #27 Tony said on the 2011/04/23 at 22:53
  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.
  
  Thanks in advance!
• 

  #28 Mark said on the 2011/04/24 at 13:20
  Is there also a console command to extract strings to be translated and to create the corresponding xliff file as in symfony 1.4?
• 

  #29 Weng said on the 2011/04/26 at 22:03
  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.
• 

  #30 Weng said on the 2011/04/27 at 21:06
  Please ignore thread #29. All sorted with PR12 release. All good now.