Should we deprecate Stable9?

Created on 11 March 2025, 22 days ago

Problem/Motivation

From @catch on Slack:

We moved stable to contrib because the recommended way to make new themes was via starterkit - [#3309392]

But at that point left stable9 in.

There is no stable10 because of starterkit. I'm not sure why core should provide stable9 when it's not going to provide stable10 or stable11, so it could move to contrib.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

🌱 Plan
Status

Active

Version

11.0 🔥

Component

Stable 9 theme

Created by

🇮🇪Ireland markconroy

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @markconroy
  • 🇮🇪Ireland markconroy

    When creating custom themes, I quite like the process of just creating the bare minimum

    • theme.info.yml
    • theme.libraries.yml
    • CSS + JS + templates as needed
    • everything else inheriting from Stable9 or some other base theme

    This means the custom theme directory is as small as possible and very easy to find your way around. Removing Stable9 would mean a change to this process. I'm not against that, but I would guess there are others that have the same process and maybe do not want a copy of every template, for example, in their custom themes.

  • 🇳🇿New Zealand quietone

    If deprecated is the intention to move it to a contributed project or just delete?

  • 🇬🇧United Kingdom catch

    @quietone we'd need to move it to a contributed project as we did for stable.

  • 🇳🇿New Zealand quietone

    @catch, thanks.

    Adding tags. Since @markconroy is the Stable9 maintainer, this already has subsystem maintainer approval.

  • 🇺🇸United States nicxvan

    I don't know that matkconroy is in favor, I think he created this to track catch's discussion, but I don't want to speak for him.

  • 🇮🇪Ireland markconroy

    I'm not totally against this idea, but I'm also not totally for it either. As @nicxvan said, I created the issue to track @catch's discussion and so that it wouldn't get lost in the Slack history.

  • 🇺🇸United States nicxvan

    Adding tag back in that case.

Production build 0.71.5 2024