oliverdavies.uk/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.yml

uuid:
  - value: f4bd3e6c-94cf-4c81-bf3a-63aa743a6639
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-05-11T09:00:20+00:00'
revision_uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: {  }
status:
  - value: true
uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
  - value: 'Major version updates are just removing deprecated code'
created:
  - value: '2024-02-14T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:20+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/02/14/major-version-updates-are-just-removing-deprecated-code
    langcode: en
body:
  - value: |
      <p>Today, I've been watching the new <a href="https://symfonycasts.com/screencast/symfony7-upgrade">Upgrading &amp; What's in Symfony 7</a> video course on SymfonyCasts.</p>

      <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>

      <p>New feature releases that contain new features are every six months.</p>

      <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>

      <p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.</p>

      <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>

      <p>This is also how Drupal releases new versions, too.</p>

      <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>

      <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>

      <h2 id="here%27s-the-thing">Here's the thing</h2>

      <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>

      <p>This means the upgrade can be split over several weeks or months to reduce the risk.</p>

      <p>Then, finally, you <em>just</em> update to the next major version.</p>

      <p>All the hard work has already been done.</p>

              
    format: full_html
    processed: |
      <p>Today, I've been watching the new <a href="https://symfonycasts.com/screencast/symfony7-upgrade">Upgrading &amp; What's in Symfony 7</a> video course on SymfonyCasts.</p>

      <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>

      <p>New feature releases that contain new features are every six months.</p>

      <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>

      <p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.</p>

      <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>

      <p>This is also how Drupal releases new versions, too.</p>

      <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>

      <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>

      <h2 id="here%27s-the-thing">Here's the thing</h2>

      <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>

      <p>This means the upgrade can be split over several weeks or months to reduce the risk.</p>

      <p>Then, finally, you <em>just</em> update to the next major version.</p>

      <p>All the hard work has already been done.</p>

              
    summary: null
field_daily_email_cta: {  }