Use a 'main' branch as the development target

Created on 23 August 2023, 10 months ago
Updated 4 May 2024, about 2 months ago

Problem/Motivation

Follow-up from 🌱 [Policy] Branch Naming: Use an 11.x branch for HEAD, then use 'main' when d.o can support it Fixed . https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-... β†’ has more of a write-up.

Drupal.org currently doesn't support having a 'main' branch since some logic is tied to version numbers, when it does, or when the relevant functionality is moved to gitlab, we should stop using 11.x as the development target and use main instead.

We're hoping this can happen before we need to open a '12.x' branch.

There are going to be core issues with having a non-numeric version too - we might have to solve that but setting Drupal::VERSION to the current major version target and updating that every so often (11, 12, 13 etc.)

The branching strategy would otherwise be the same as the current one with '11.x'.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🌱 Plan
Status

Active

Version

11.0 πŸ”₯

Component
BaseΒ  β†’

Last updated 1 minute ago

Created by

πŸ‡¬πŸ‡§United Kingdom catch

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

Comments & Activities

Production build 0.69.0 2024