Problem/Motivation

See https://www.drupal.org/core/experimental#beta

  • We will be API stable - all main API classes will have @internal removed
  • Config Transformation event API will have been moved to core

Proposed resolution

Ensure we're ready for the beta gates - ie. API stability, deprecations and upgrade paths.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

alexpott created an issue. See original summary.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Issue summary: View changes
alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Parent issue: » #3033427: [plan] Add support for environment-specific configuration
xjm’s picture

xjm
she/her
Primary language English
commented

We shouldn't be moving anything into core namespaces until the module is being marked stable, unless the functionality would be added even without the experimental module existing. Otherwise, it's beta code in a stable namespace.

bircher’s picture

bircher
Location 🇨🇿
commented

I absolutely agree with #4.
We are in the second case with #2991683: Move configuration transformation API in \Drupal\Core\Config namespace and #3079029: Move module config exclusion from config_environment to core.services:
While we are still working on the config_environment module and what was planned for it, in the mean time we used it to solve the chicken-egg problem with having the api without using it. Since we now have a use for the API in core outside of the config_environment module, the API can go into core also without the experimental module.

We can remove @internal from \Drupal\Core\Config\ImportStorageTransformer which is the only API class one is expected to use.
Ie \Drupal::service('config.import_transformer')->transform($myStorage);
The other direction is covered by \Drupal\Core\Config\StorageInterface when using the config.storage.export service.

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.

bircher’s picture

bircher
Location 🇨🇿
commented
Version: 8.9.x-dev » 9.1.x-dev

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.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.