About symfony 1.3 and symfony 1.4

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

Comments

Thank you for providing an easy to use upgrade mechanism from 1.0 to 1.4
Very good news! It definately makes sense to go that way.

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.
@Matthias You can see a description of the current branches on the installation page. Symfony 1.3 is unstable, but we would welcome any feedback.
When is Symfony 2.0 planned to be released?
@Javi i think it will be released near Q2 2010... but i wish it could be faster :D
Good news! I was looking forward next LTS.

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.
I love the work you guys are doing, and am excited to hear about the arrival of a new LTS release.

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?
I am looking to use symfony for a new project where I am helping out the un-informed.org effort (http://pooteeweet.org/blog/1521).

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.
Plus, to add to my last comment, project:freeze significantly simplifies my team's management of symfony upgrade deployment when used in tandem with project:deploy.
I like how 1.4 is just like 1.3 but without the depcrecated code. Seems like a good strategy that is easy to understand.

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.