[META] Remove outdated references to "upgrade" from core

Open on Drupal.org →

Created on 19 April 2016, over 8 years ago

Updated 5 August 2023, over 1 year ago

Follow-up to #2701541: Rename Drupal Upgrade UI to Migrate Drupal UI →

Problem/Motivation

"Upgrading" previously referred to using update.php to go from one major version to the next, and was distinguished from "updating" (using update.php to go from one patch/minor version to the next).
The difference between "upgrading" and "updating" was always confusing to most people including core devs, and Migrate is a drastically different process both internally and for site owners.
#2701541: Rename Drupal Upgrade UI to Migrate Drupal UI → fixes the name of the Migrate Drupal UI module in this regard, but left behind some other uses of "Upgrade" within the module:

There may be other stale references in core as well.

Proposed resolution

Find all instances of "upgrade", "upgrading", etc. Replace with consistent terminology that is more consistent when appropriate (e.g., referring to major- or minor-version updates).

Remaining tasks

TBD

User interface changes

TBD (some at least in the Migrate Drupal UI).

API changes

TBD

Data model changes

TBD

🌱 Plan

Status

Active

Version

11.0 🔥

Component

Last updated about 2 hours ago

Created by

🇺🇸United States xjm

Live updates comments and jobs are added and updated live.

Usability
Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Needs usability review
Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

Incomplete comments

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.

Comment almost 2 years ago →
🇺🇸United States smustgrave
Drupal core no longer supports "upgrading" a site between major versions; instead, core supports migrating content and configuration from an old D6/7 site into a separate D8 site.

Shouldn't the word in this context include migration? May also want to consider how https://www.drupal.org/project/upgrade_status → uses their terminology since that tool has been popular for going from D9 to D10.

But this seems like a plan or idea discussion now.
Status changed to Active over 1 year ago4:43pm 14 July 2023
Comment over 1 year ago →
🇺🇸United States xjm
Plan sounds good.
Comment over 1 year ago →
🇺🇸United States xjm
Removed some of the old stuff from the IS.
Comment over 1 year ago →
🇳🇿New Zealand quietone
Haven't seen this issue in a while.

Drupal would not be alone in using 'upgrade' for major version changes and 'update' for minor. Here are some relevant links.

https://ubuntu.com/server/docs/upgrade-introduction
https://fossbytes.com/whats-the-difference-between-update-and-upgrade/
https://wordpress.org/documentation/article/updating-wordpress/
https://wordpress.org/documentation/article/upgrading-wordpress-extended...
https://docs.joomla.org/Portal:Upgrading_Versions

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024