Problem/Motivation

We have lots of deprecated code kicking around now, and we probably don't actually work with Drupal 8 or 9 tbh. So maybe we should go for broke and do a 2.x version of the module, maybe semver, and declare ourselves fairly restrictive in what we support.

Steps to reproduce

Look at the codebase, just look at it!

Proposed resolution

Make a 8.x-2.x branch, and remove lots of deprecated code, bump the minimum core version, but otherwise change nothing between 8.x-1.5 and that.

Remaining tasks

Do all the work.

User interface changes

None.

API changes

Deprecations.

Data model changes

None.

Issue fork kraken-3586745

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

steven jones created an issue. See original summary.

steven jones’s picture

steven jones commented
Version: 8.x-1.x-dev » 8.x-2.x-dev

steven jones opened merge request !11

  • steven jones committed 482a530e on 8.x-2.x 
    task: #3586745 Drop support for < drupal:10.3.

by: steven jones
steven jones’s picture

steven jones commented
Title: Drop support for < 10.4? » Drop support for < drupal:10.3?
Status: Active » Fixed

Done!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.