Problem/Motivation

See #2863188: Hardcoded result size limit in the entity reference autocomplete widget. for discussion.

See https://api.drupal.org/api/drupal/core%21modules%21views%21views.module/... for an example already in core that is missing this.

Proposed resolution

Inside the backwards compatibility layer, trigger an error when configuration needs to be update, stating that the bc layer will be removed in 9.x (if issues land after 8.8.0 then we should make the deprecation for 10.0.x).

Remaining tasks

Find more examples. Also document this pattern properly at https://www.drupal.org/core/d8-bc-policy

User interface changes

API changes

Data model changes

Release notes snippet

Comments

catch created an issue. See original summary.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Title: Add proper deprecation notices in config entity presave bc layers » [policy] Add proper deprecation notices in config entity presave bc layers

Is the bc policy the right place for this?
The deprecation policy already has a section for Code paths & behavior that covers this case. Although that section does need an example. Is that sufficient? Does the hook_ENTITY_TYPE_presave() need to be mentioned specifically?

catch’s picture

It should go in https://www.drupal.org/about/core/policies/core-change-policies/drupal-d...

I got caught out by this myself recently, will find the issue and link it here...

xjm’s picture

catch’s picture

Status: Active » Closed (duplicate)
Related issues: +#3443942: Add proper deprecation notices in config entity presave bc layers

Marking duplicate of #3443942: Add proper deprecation notices in config entity presave bc layers which is a much newer duplicate issue opened by me, but has more up-to-date info on it.

quietone’s picture

Version: 11.x-dev » 11.0.x-dev

Changing to latest version when this was closed.

quietone’s picture

xjm’s picture