tome export
This commit is contained in:
parent
52278c3a53
commit
7a52afab5f
960 changed files with 3670 additions and 2229 deletions
|
|
@ -82,15 +82,15 @@
|
|||
],
|
||||
"body": [
|
||||
{
|
||||
"value": "\n <p>Today, I've been watching the new <a href=\"https:\/\/symfonycasts.com\/screencast\/symfony7-upgrade\">Upgrading & What's in Symfony 7<\/a> video course on SymfonyCasts.<\/p>\n\n<p>The first video - <a href=\"/podcast\/10-ryan-weaver-symfonycasts\">recent podcast guest Ryan Weaver<\/a> - explains how Symfony's release cycle works.<\/p>\n\n<p>New feature releases that contain new features are every six months.<\/p>\n\n<p>Along with the x.4 release - such as Symfony 6,4 - there is also a new major release - in this case, Symfony 7.<\/p>\n\n<p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.<\/p>\n\n<p>So, updating from Symfony 6.4 to 7 means you just need to remove any deprecated code from your application and make it work in the Symfony 7 way.<\/p>\n\n<p>This is also how Drupal releases new versions, too.<\/p>\n\n<p>New releases, like Layout Builder, are added in minor versions like 8.1, and Drupal 9 is Drupal 8 without its deprecated code.<\/p>\n\n<p>Because the code in major versions is so similar, <strong>contributed modules and themes can support multiple major versions at the same time<\/strong>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When upgrading projects from Drupal 8 to 9 and 9 to 10, the majority of the work can be done beforehand by keeping up to date with module releases and updating custom code to remove any deprecations.<\/p>\n\n<p>This means the upgrade can be split over several weeks or months to reduce the risk.<\/p>\n\n<p>Then, finally, you <em>just<\/em> update to the next major version.<\/p>\n\n<p>All the hard work has already been done.<\/p>\n\n ",
|
||||
"value": "\n <p>Today, I've been watching the new <a href=\"https:\/\/symfonycasts.com\/screencast\/symfony7-upgrade\">Upgrading & What's in Symfony 7<\/a> video course on SymfonyCasts.<\/p>\n\n<p>The first video - <a href=\"\/podcast\/10-ryan-weaver-symfonycasts\">recent podcast guest Ryan Weaver<\/a> - explains how Symfony's release cycle works.<\/p>\n\n<p>New feature releases that contain new features are every six months.<\/p>\n\n<p>Along with the x.4 release - such as Symfony 6,4 - there is also a new major release - in this case, Symfony 7.<\/p>\n\n<p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.<\/p>\n\n<p>So, updating from Symfony 6.4 to 7 means you just need to remove any deprecated code from your application and make it work in the Symfony 7 way.<\/p>\n\n<p>This is also how Drupal releases new versions, too.<\/p>\n\n<p>New releases, like Layout Builder, are added in minor versions like 8.1, and Drupal 9 is Drupal 8 without its deprecated code.<\/p>\n\n<p>Because the code in major versions is so similar, <strong>contributed modules and themes can support multiple major versions at the same time<\/strong>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When upgrading projects from Drupal 8 to 9 and 9 to 10, the majority of the work can be done beforehand by keeping up to date with module releases and updating custom code to remove any deprecations.<\/p>\n\n<p>This means the upgrade can be split over several weeks or months to reduce the risk.<\/p>\n\n<p>Then, finally, you <em>just<\/em> update to the next major version.<\/p>\n\n<p>All the hard work has already been done.<\/p>\n\n ",
|
||||
"format": "full_html",
|
||||
"processed": "\n <p>Today, I've been watching the new <a href=\"https:\/\/symfonycasts.com\/screencast\/symfony7-upgrade\">Upgrading & What's in Symfony 7<\/a> video course on SymfonyCasts.<\/p>\n\n<p>The first video - <a href=\"/podcast\/10-ryan-weaver-symfonycasts\">recent podcast guest Ryan Weaver<\/a> - explains how Symfony's release cycle works.<\/p>\n\n<p>New feature releases that contain new features are every six months.<\/p>\n\n<p>Along with the x.4 release - such as Symfony 6,4 - there is also a new major release - in this case, Symfony 7.<\/p>\n\n<p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.<\/p>\n\n<p>So, updating from Symfony 6.4 to 7 means you just need to remove any deprecated code from your application and make it work in the Symfony 7 way.<\/p>\n\n<p>This is also how Drupal releases new versions, too.<\/p>\n\n<p>New releases, like Layout Builder, are added in minor versions like 8.1, and Drupal 9 is Drupal 8 without its deprecated code.<\/p>\n\n<p>Because the code in major versions is so similar, <strong>contributed modules and themes can support multiple major versions at the same time<\/strong>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When upgrading projects from Drupal 8 to 9 and 9 to 10, the majority of the work can be done beforehand by keeping up to date with module releases and updating custom code to remove any deprecations.<\/p>\n\n<p>This means the upgrade can be split over several weeks or months to reduce the risk.<\/p>\n\n<p>Then, finally, you <em>just<\/em> update to the next major version.<\/p>\n\n<p>All the hard work has already been done.<\/p>\n\n ",
|
||||
"processed": "\n <p>Today, I've been watching the new <a href=\"https:\/\/symfonycasts.com\/screencast\/symfony7-upgrade\">Upgrading & What's in Symfony 7<\/a> video course on SymfonyCasts.<\/p>\n\n<p>The first video - <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">recent podcast guest Ryan Weaver<\/a> - explains how Symfony's release cycle works.<\/p>\n\n<p>New feature releases that contain new features are every six months.<\/p>\n\n<p>Along with the x.4 release - such as Symfony 6,4 - there is also a new major release - in this case, Symfony 7.<\/p>\n\n<p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.<\/p>\n\n<p>So, updating from Symfony 6.4 to 7 means you just need to remove any deprecated code from your application and make it work in the Symfony 7 way.<\/p>\n\n<p>This is also how Drupal releases new versions, too.<\/p>\n\n<p>New releases, like Layout Builder, are added in minor versions like 8.1, and Drupal 9 is Drupal 8 without its deprecated code.<\/p>\n\n<p>Because the code in major versions is so similar, <strong>contributed modules and themes can support multiple major versions at the same time<\/strong>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When upgrading projects from Drupal 8 to 9 and 9 to 10, the majority of the work can be done beforehand by keeping up to date with module releases and updating custom code to remove any deprecations.<\/p>\n\n<p>This means the upgrade can be split over several weeks or months to reduce the risk.<\/p>\n\n<p>Then, finally, you <em>just<\/em> update to the next major version.<\/p>\n\n<p>All the hard work has already been done.<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
"feeds_item": [
|
||||
{
|
||||
"imported": "1970-01-01T00:33:45+00:00",
|
||||
"imported": "1970-01-01T00:32:50+00:00",
|
||||
"guid": null,
|
||||
"hash": "f974bdb7342e7a84aac0ceb4a74dbdfa",
|
||||
"target_type": "feeds_feed",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue