Explore >> Select a destination
|
You are here 
|
www.tobymackenzie.com | ||
| | | | |
tomasvotruba.com
|
|
| | | | | There are two types of upgrades. One follows only `UPGRADE.md` files on every release, replacing what has been removed with new alternatives. It works, and we could say that the codebase will be "up-to-date." The other upgrade doesn't stop at the required minimum but **makes use of all modern features the framework provides**. It will be faster, easier to understand, and easier to upgrade to the next version. I [wrote a post](/blog/two-kinds-of-legacy-code-upgrade) that explains why the latter is better. There are no sources about Symfony upgrades spanning multiple major versions-time to fix that. | |
| | | | |
brunty.me
|
|
| | | | | Developer and problem solver | |
| | | | |
gist.github.com
|
|
| | | | | Migration guide to Symfony 3 LTS. GitHub Gist: instantly share code, notes, and snippets. | |
| | | | |
tomasvotruba.com
|
|
| | | During Easter weekend, usually, people take a break and have a rest. Instead, we used these 4 days of *holiday* to migrate the 304-controller application. At least that was the goal on Friday. Me in my colleague in the migrated project accepted the challenge. We got into many minds and code-traps. We'd like to share this experience with you and **inspire those who are still stuck on non-MVC code** and think it might take weeks or even months to switch to a framework. | ||
