Make 2.0.x branch default in gitlab

Created on 6 August 2024, 8 months ago

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

2.0

Component

Code

Created by

ivnish Kazakhstan

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

Comments & Activities

  • Issue created by @ivnish
  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia

    Only @RdeBoer has permissions to do this. (It needs 'administer maintainers' permission for this project, which only he has.)

    Also see πŸ“Œ Release with Drupal 11 support Needs work . I plan to make a new branch 2.1.x where we can drop D9 support and add D11 support, that way we can continue to support existing sites with the old branch without breaking anything. In that case, the GitLab default should be the new 2.1.x branch, when it exists.

  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia
  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia
  • πŸ‡ΊπŸ‡ΈUnited States nicxvan

    You should be able to create the 2.1.x release even if it is not the base branch.

    The only thing the base branch affects really is which branch future MRs come from.

    Have you reached out to @RdeBoer on slack? He doesn't look too active on D.O recently.

  • Assigned to rdeboer
  • Status changed to Needs review 6 months ago
  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia

    Yes thank you. I can tell @RdeBoer hasn't logged in a many months because his user name hasn't been mangled and turned into a machine name yet - it still has capital letters in it.

    Regardless, this is not a pressing issue because there is no release yet on 2.1.x. When it does become an issue, I will take additional steps to get this done, as I have many times in the past with many other projects.

  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia

    @RdeBoer took care of this. Thank you!

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

Production build 0.71.5 2024