- What is Symfony?
- Get started
- Documentation
- Community
- Services
-
News
Latest News
What happened last week in Symfony?
This week, the new Symfony 2.3 branch was created. In addition, the first Symfony 2.3 release candidate version was published, which includes tons of great small improvements. Lastly, one of the biggest Symfony events of the year, the Symfony Live Portland 2013 conference, will take place next week.
Upcoming EventsThe Symfony Community organizes events all over the world on a regular basis. Here are the next ones.
France, Montpellier — eZ UnConference #2
from May 27, 2013 to May 29, 2013
Germany, München — Symfony User Group München
on June 05, 2013, from 18:30 to 22:30
Germany, Köln — Symfony User Group Cologne steht an!
on June 05, 2013, from 19:00 to 22:00
Spain, Madrid — deSymfony 2013
from June 21, 2013 to June 23, 2013 - About
Archives
Master Symfony2 fundamentals
Symfony hosting done right
Discover the SensioLabs Support
About symfony 1.3 and symfony 1.4
by
Kris Wallsmith
– August 06, 2009
– 10 comments
The January 2010 end of maintenance for symfony 1.0 is fast approaching. Though we may feel a certain attachment to this first stable release of symfony, discontinuing its support is a natural step in the evolution of the project.
Of course, symfony 1.0 is not only around for sentimental reasons, it is also the current release with long term support from the symfony team. Once this support period expires, our next LTS release will be symfony 1.4, which we will support until January 2013. Symfony 1.4 will be the last release in the 1.x branch, which means the next LTS release after that will be Symfony 2.
symfony 1.4 = symfony 1.3 - deprecated stuff
This is the equation Fabien has used to describe symfony 1.4. It's a pretty simple equation, which is why we're planning to release symfony 1.4 either with or on the heels of symfony 1.3. Once these versions are released, we recommend new projects use symfony 1.4 and older projects that use deprecated features upgrade to symfony 1.3.
Also, since the two versions will be very similar, I will be filling the role of Release Manager for both of them.
To recap:
| Version | Release | Support |
|---|---|---|
| symfony 1.3 | late 2009 | November 2010 |
| symfony 1.4 | late 2009 | January 2013 |
NEWS FROM THE BLOG
IN THE NEWS
is a trademark of Fabien Potencier. All rights reserved.
Add a Comment
Comments
Are there any new major features or changes intended to be added to these releases until December?
Is there a roadmap of some planned features?
I ask because I wonder if it makes sense to already try sf 1.3 for a new project. Should work when I have tests and only use a certain revision, shouldn't it.
I've begun reading DEPRECATED_IN_1_3 to be ready to use symfony 1.4.
By the way, I'm worried by your following sentence:
> Symfony 1.4 will be the last release in the 1.x branch, which means the next LTS release after that will be Symfony 2.
I wanna use Symfony 2 because that must be better than symfony 1.x. So I hope to agree with this decision.
But, I wonder about Symfony 2 ... because we cannot see developing Symfony 2. I cannot judge that Symfony 2 is really good. And I cannot judge about LTS release.
Can you show developing Symfony2 to us? I really interest to that.
My only reservation, having read the document about deprecated functionality is the removal of the `project:freeze` and `project:unfreeze` tasks... My development team makes heavy use of it in our workflow because it really simplifies things.
But maybe I'm overlooking something. Does removing these tasks really simplify anything?
Does it make sense to start using 1.3 there? Since in my first steps I want to work with the admin generator, I wonder how solid this component is atm. The other thing is, I havent used symfony in a while, but I assume I can make sure that deprecation notices will be shown in bold letters, so that I can avoid using stuff that will be dropped in 1.4 from the get-go.