Problem/Motivation

This is a meta/plan issue to keep track of what's needed to make Stable a reality.

The Plan

  1. #2575421: Add a Stable base theme to core and make it the default if a base theme is not specified is in, this means a theme created without specifying a base theme in its *.info.yml will use Stable as the base.
  2. We are working on #2575737: Copy templates, CSS, and related assets to Stable and override core libraries' CSS, this makes Stable a snapshot (which can still be updated to fix bugs) of 8.0.0-rc1 core markup, CSS, and related assets (images/vectors referenced from CSS).
  3. #2580049: Removed CSS files not removed from library definitions blocks #2 going in because it makes the library override tests fail until we update our library definitions to reflect reality.
  4. We are working on #2581443: Make Classy extend from the new Stable base theme.
  5. After 2, 3, and 4 are completed we can update Classy's Twig extends, library overrides etc. in #2588289: Update Classy's Twig extends now that it extends from Stable. We want to do this sooner than later for people that will copy/override Classy's templates.
  6. We can probably update Bartik and Seven's extends/overrides after 5 in separate issue(s) since they are internal.

Comments

Cottser created an issue. See original summary.

star-szr’s picture

star-szr
he/him
Primary language English
commented
Issue summary: View changes
star-szr’s picture

star-szr
he/him
Primary language English
commented
Issue summary: View changes
star-szr’s picture

star-szr
he/him
Primary language English
commented
Issue summary: View changes
joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Active » Fixed

Finito

star-szr’s picture

star-szr
he/him
Primary language English
commented
Status: Fixed » Active

Still need to make a couple issues to update Bartik and Seven I think.

droplet’s picture

droplet commented

Any DOCs about Stable theme? and how to patch it if we find bugs ?

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

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

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.

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented
Status: Active » Fixed

All of the child issues are finished so marking this as fixed as well. Crediting @Cottser for all the coordination.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.