[policy, no patch] Backport policy for Starterkit theme changes

Created on 23 September 2022, over 2 years ago
Updated 23 April 2025, 1 day ago

Problem/Motivation

The current backport policy only allows changing CSS, markup, or template changes in a minor. This doesn't take into account that Starterkit theme CSS, markup, and templates are not something sites rely on runtime.

Proposed resolution

Change the backport policy to allow backporting CSS, markup, and template changes that are required for fixing bugs in the Starterkit theme. New features and code refactoring are not backported to patch releases.

📌 Task
Status

Needs review

Version

11.0 🔥

Component

Starterkit theme

Created by

🇫🇮Finland lauriii Finland

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇳🇿New Zealand quietone

    The allowed changes for minor releases does list CSS, markup, or template changes (except for stable base themes) for minor releases. However, the allowed changes for patch releases states that "non-disruptive bug fixes" are allowed. So, the fixes described in the issue summary would fit within the existing criteria.

    An extra sentence could be added to explain that changes to Starterkit are not disruptive. However, Disruptive is defined later in the document and can be evaluated in any issue or amongst the core committers. Also, there is always tension in such documents to provide both detail and flexibility in interpretation. I would rather leave the policy as is.

Production build 0.71.5 2024