Problem/Motivation

A lot of 9.x issues are 'remove deprecated function X'. We probably will not want to do those as 300 individual patches when 8.x opens up.

Proposed resolution

For any removal that is simply deleting dead, deprecated code, mark it as duplicate of this issue.

When it comes time to open the 9.x branch, we can probably handle all the straightforward deletions with a single patch.

Then we can make this issue one of the ones that is RTBC and ready to land on the day 9.x opens.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue. See original summary.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch as a volunteer commented
Issue summary: View changes
catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch as a volunteer commented
Title: Removing 9.0.0 deprecations » Removing 9.0.0 deprecated methods and functions
catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch as a volunteer commented
Status: Active » Closed (duplicate)

Doh, had this idea twice #2716163: [META] Remove deprecated classes, methods, procedural functions and code paths outside of deprecated modules on the Drupal 9 branch

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.