3 years after: symfony 1.0 Last release!
Published by
Grégoire Hubert
Grégoire Hubert
ttp://www.prototypejs.org/2007/3/9/prototype-1-5-1-rc1#comment-14760
Now we should say goodbye to 1.0 and step forward to 1.4? How shall we upgrade the whole application with dozens of modules, libs and so on. I really like to upgrade, but I dont know how. I don´t find any upgrade process from 1.0 to 1.4. What shall we do? Rewrite all the code we have coded?
Maik
I agree with Alexis-b and MaikL. There are still a lot of (large) symfony 1.0 projects. Migrating these projects to 1.4 will be cost- and time-intensive.
Imho its a must to have a "migration plan" (documentation) from 1.0.x to 1.4 because a lot of people skipped the 1.1 and 1.2 releases.
If you would have cared about the end of support day, you would have been able to discover upgrade options over the last years.
symfony is upgradeable! there is no need to rewrite much. Especially if you have good code. But there might be cases where an upgrade is painful. Perhaps the most important part is the propel upgrade from 1.2 to 1.3. Form validation is the other big one.
Going from 1.0 to 1.3 should be easy (1.4 is another story). Check how you would upgrade to 1.1, 1.2 and 1.3 one by one.
So, no worries, and good luck.
Daniel
announced a long time ago; well, 3 years ago to be precise. And since then, we
have always provided a migration path to ease upgrading your applications from
the previous version to the next one. In fact, you are quite lucky to do this
now as many other people have already migrated their applications. So, many
people will be able to help you in your job on the forum and the mailing-list.
Anyway, to upgrade from 1.0 to 1.3, first upgrade to 1.1
(http://www.symfony-project.org/installation/1_1/upgrade), then upgrade to 1.2
(http://www.symfony-project.org/installation/1_2/upgrade), and finally,
upgrade to 1.3 (http://www.symfony-project.org/tutorial/1_4/en/upgrade - docs
for 1.3 and 1.4 are the same). Eventually, you will be able to move to 1.4 by
removing your usage of deprecated features (but as Fabian said before, this is
probably the hardest thing).
If you also want to read about the new features
(http://www.symfony-project.org/blog/2008/06/30/the-wait-is-over-symfony-1-1-released,
http://www.symfony-project.org/tutorial/1_2/en/whats-new,
http://www.symfony-project.org/tutorial/1_4/en/whats-new), the deprecated ones
(http://www.symfony-project.org/tutorial/1_4/en/deprecated) and more
(http://www.symfony-project.org/doc/1_4/), we also have written documentation
about that.
The code for symfony 1.1, 1.2, 1.3, and 1.4 is available in the Subversion
repository, as archives, or as PEAR packages
(http://www.symfony-project.org/installation). That's plenty of options to
choose from.
Good luck!
I am a serious fan of 1.0 branch in which I have spent so many nights tweaking the admin generator classes for instance that I did not have time anymore to follow every new coming version.
Now I will go on 1.4, refactoring all my stuff, trying to release some strong plugins as many others.
That said, it is funny to see the race competition and the fear of some programmers not being up to date with the last sf release.
In my opinion, it's no problem using 1.0 in many cases and still for some days... After all, this is the more stable release of all 1.x releases, don't you think ?
And for "big" projects that are evolving, sure you cannot go from a 1.0 propel project to a 1.4 doctrine one (for instance) just clicking the "upgrade" button.
A lot of work is to be done, but it's so good having a lively tool such as Symfony to do the job.
So, for every LTS, hip hip hip ! houra !
And congratulations to the contributors
Loïc
But I'm sure that it will be a great help for many SF users if you merge these N documents into one, explaining what is different between these 2 major releases.