Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
While working on updating the Packages.org description text for the drupal/recommended-project project page in #3354453: Add Drupal 'keywords' to Recommended Drupal project composer.json, and update description I see that the default versions on https://github.com/drupal are quite old for most repositories.
It is best practice to make the latest official release (10.0
) or dev-release (10.1
) the default branch on Github and Gitlab, for many different reasons:
- To show the latest updated README.md and relevant information
- To make sure services which pull data from those repos get the right info
- For better SEO
- To make it clear which repos are outdated, and point to the relevant repos
Steps to reproduce
- Visit some of the repos under https://github.com/drupal and see that the default version for some of them is quite old, like Drupal 8.8 or Drupal 9.1.
- See that many of the currently 40 repositories are deprecated, yet you can't tell that from the README file. See for example drupal/pinned-dev-dependencies (#3090684: Rename drupal/dev-dependencies and drupal/pinned-dev-dependencies).
Proposed resolution
- Update the default version to the current official release for relevant repos at every minor version release of Drupal 10.1, 10.2, etc.
- Update or add README file, stating prominently at the top if the repo is outdated, and link to the relevant replacement repo
Remaining tasks
- ✅ done - Update http://drupal.org/ to https://drupal.org/ on https://github.com/drupal
- ✅ done - Update the default versions to the latest release, or dev-release
- Update README file, stating at the top if the repo is deprecated, possibly link to relevant replacement
- Make sure the default version of relevant repositories are updated to the current official release, by adding this task to the checklist when minor versions of Drupal (10.1, 10.2, etc.) are released every half year or so
Comments
Comment #2
ressa CreditAttribution: ressa at Ardea commentedComment #3
drummThis is done now.
Comment #4
drummIt looks like we could update the default branch automatically with GitHub’s API https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#update.... (I don't see a way to do this with Git commands.)
Comment #5
drummI believe using that API would be best in https://bitbucket.org/drupalorg-infrastructure/subtree-splitter/src/mast...
Comment #6
ressa CreditAttribution: ressa at Ardea commentedAdd extra task about updating deprecated repo README's:
Comment #7
ressa CreditAttribution: ressa at Ardea commentedComment #8
ressa CreditAttribution: ressa at Ardea commentedThanks for looking into this @drumm, updating the relevant repos via API would be nice. Most of the still used, recently updated repos have defaults on 8.x: https://github.com/orgs/drupal/repositories?type=all
I just looked at the Drupal Composer Scaffold, which is still on the old version. These are some important differences in the README displayed (8.x) and 11.x:
Comment #9
drummI’ve updated the default branches to 11.x
Comment #10
ressa CreditAttribution: ressa at Ardea commentedBeautiful, thanks @drumm!
Maybe it would be worth adding to a checklist, to remember to repeat the process, when the Drupal 12 branch is created? Anyway, the main tasks here are solved, so changing status. (Unless you think the "Update README file with deprecated text" item is relevant ...)