Problem/Motivation

The 9.x branch of core is just a placeholder to allow project_issue to display it in the version selector. However, contributors are occasionally confused by the existence of the 9.x branch. See, for example, #2863957: Drupal 9.x installation doesn't work properly.

Proposed resolution

Replace 9.x with only a README file.

Remaining tasks

  • git ls-files -z | xargs -0 git rm
  • Add the attached README.txt.
  • Commit and push.

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
README.txt216 bytesxjm
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

xjm created an issue. See original summary.

alexpott’s picture

So when we start developing Drupal 9 we'd:

  1. Create a new branch called 9.0.x from whatever Drupal 8.x.x branch we're up to.
  2. Create a new branch from 9.x called 10.x and update the readme?
  3. Maybe do a force push to delete the 9.x branch?
cilefen’s picture

Issue summary: View changes

git ls-files -z | xargs -0 git rm works better if the working copy has any untracked files.

cilefen’s picture

Re #2 why 10.x not 10.0.x?

alexpott’s picture

@cilefen because if we make the placeholder branch 10.0.x then we have to force delete it when in comes time to branch 9.x.x to open the 10.0.x branch - which messes with git history.

cilefen’s picture

Oh, exactly, I get it now.

Chi’s picture

I wonder if removing all files from the branch and then pushing them again at some point will have much impact on overall size of the repository.

djalxs’s picture

This shouldn't have much of an effect on repository size, compared to the size it already is.

I would say this needs to be done pretty much immediately, as I myself have just installed using the 9.x branch and was confused as to why 9.x looks more like 7.x than 8.x does and why it has so much functionality missing.

At what point will we have a working 9.0.x dev branch? I'm quite enthusiastic to contribute to be honest.

djalxs’s picture

The mind also boggled at why that disgusting 'Overlay' module was back.

Urrrgh.

cilefen’s picture

@djalxs I am glad you are enthusiastic. There is much still to innovate in Drupal 8—please help there. I understand the confusion to a degree, however, I am not aware of anything on drupal.org indicating that development on Drupal 9 has begun. Some related reading:

xjm’s picture

Title: Make the 9.x branch empty » Delete the 9.x branch and its associated release
Project: Drupal core » Drupal.org infrastructure
Version: 9.x-dev »
Component: other » Git
Status: Needs review » Postponed

9.0.x will be branched in about seven days, so there's no longer any value in doing anything with the legacy 9.x branch. Retitling accordingly, and moving to (hopefully) the correct infra queue. This issue is postponed on 9.0.x opening and a bulk update happening to move the 9.x issues to 9.0.x.

Gábor Hojtsy’s picture

Status: Postponed » Active

#3087223: Bulk update 8.7.x & 8.8.x Drupal core issues for 8.9.x AND 9.0.x! migrated all the 9.x issues to 9.0.x. I don't believe there is anything else left to postpone this on? I will not do the branch removal myself though to make sure to check with all respective parties that it is a go!

People are getting confused, such as

Gábor Hojtsy’s picture

Also there is apparently no 9.x tarball / release anymore, just the branch.

drumm’s picture

Project: Drupal.org infrastructure » Drupal core
Version: » 9.0.x-dev
Component: Git » other
Status: Active » Reviewed & tested by the community

I deleted the release shortly after issue migration, so no issues got back to the 9.x version.

Go ahead and push deletion of the 9.x branch whenever you’d like, or let me know if I should take care of that.

xjm’s picture

Status: Reviewed & tested by the community » Fixed

I pushed the 9.x branch deletion earlier today. Thanks everyone!

Status: Fixed » Closed (fixed)

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