Problem/Motivation

Following #2822727: [policy, no patch] Adopt a continuous API upgrade path for major version changes, 9.x should only drop deprecated APIs from 8.x

This means that at least theoretically, 99% of 8.x modules that are not using deprecated APIs will run on 9.x.

However, the core key in .info.yml only supports a single version. To allow modules to run on two or more versions, we should allow that to take a version range. We already have versioned dependencies for modules so may be able to re-use some of that code (or at least find out why we can't).

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue. See original summary.

catch’s picture

Title: Add capacity for modules to specify compatibility with two+ major versions » Add capability for modules to specify compatibility with two+ major versions
Mixologic’s picture

It would be nice if the core key could begin to be interpreted, internally, just like any other dependency, and begin to allow the same kinds of dependency constraints as are allowed in other dependency declarations.

I would strongly suggest that fixing the dependency constraint parsing code to support semantic versioning would be a blocker to this: #2641658: Module version dependency in .info.yml is ineffective for patch releases

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Gábor Hojtsy’s picture

Issue tags: +Drupal 9
Gábor Hojtsy’s picture

Status: Active » Closed (duplicate)

Actually this is the same as #2807145: [policy, no patch] Allow contrib projects to specify multiple major core branches, closing in favor of that. Will copy over the comment from @Mixologic.