The process has five phases:

• Phase 1: 90 days before EOL
  Communication on the end of life for the Drupal version.
• Phase 2: 14 days before EOL
  Activation of a blocker in the CI/CD 14 days before the version is marked as unsupported by Drupal.org. This block is automatically generated from the constraint encoded in the Quality Assurance website. Manual bypass is possible on-demand for business needs, if approved by a DIGIT. D1.004 official.
• Phase 3: EOL
  End of life Drupal version, meaning the date when Drupal.org marks the version as unsupported.
• Phase 4: 90 days after EOL
  Application of business restrictions 90 days after EOL to the non-compliant projects. We will block the authentication to any request from outside the trusted network (EC). Some additional restrictions can be imposed depending on the project and issue nature. A shorter period can be configured based on security vulnerabilities that would appear for newer versions.
• Phase 5: 180 days after EOL
  180 days after EOL, the website will be moved into a “static version”. DIGIT does not guarantee the functionality of the website as it is likely that some features of the website are lost in the process of static HTML conversion.

The timeframe mentioned in the previous phases can be shortened if security vulnerabilities in newer versions are detected.