Problem/Motivation

Drupal 8 introduces the concept of an "experimental" module (in a "Core (experimental)" package), which indicates that a module is shipped with core but not fully supported. We plan to rely more on this concept as we add new optional functionality in minor versions. However, there is currently not enough explanation of what this means for site users or developers.

  1. There is no definition of what "experimental" actually means.
  2. Experimental modules should have separate versions than core -- alpha, beta, etc.
  3. There is no obvious warning when you enable an experimental module -- just an innocuous-seeming success message. And enabling the module via (e.g.) Drush won't even have had the information from the group label that core does (see above screenshot).
  4. The status report does contain the needed warning, but could use a link to more details (the aforementioned handbook page).
  5. The help page might also benefit from a note about the module being experimental, and known issues should be documented (there or somewhere else).

Proposed resolution

  1. #2657062: [policy, no patch] Experimental module policy and handbook page
  2. #2656994: Experimental modules should have their own version numbers
  3. Expand/highlight experimental module group info or info when version differs from core's?
  4. #2663796: Use a confirmation form when enabling experimental modules
  5. #2657096: Provide a link to the experimental module policy in the status report warning
  6. #2657178: Warn about experimental modules on their help pages
  7. Document known issues for help?
  8. Standardize on experimental module section for release notes? (Known issues, version, etc.)
  9. Propose Drush issue for warning about enabling experimental modules?

Remaining tasks

File child issues.

CommentFileSizeAuthor
migrate_help.png42.95 KBxjm
mirgrate_status_report.png46.27 KBxjm
migrate_no_warning.png48.48 KBxjm
migrate_no_definition.png33.11 KBxjm

Comments

xjm created an issue. See original summary.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes

Added #2663796: Use a confirmation form when enabling experimental modules.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

xjm’s picture

xjm
she/her
Primary language English
commented
Version: 8.2.x-dev » 8.1.x-dev

This meta is mostly about the imminent minor, so moving back.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Closed (outdated)

We've been doing this for years now. I'm pretty sure there's no work left here.