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.We no longer support using upgrade.php for major version upgrades. Accordingly, the section of UPGRADE.txt that deals with major version upgrades needs to be revised.
Actually, most of the text should be removed, and replaced with one sentence saying that it is not possible to upgrade a site from one major version to another in place, and that what you have to do instead is build a new Drupal 8 site, and then use the Migrate module to migrate your data from the old version of Drupal to the new site.
The rest of this is the original issue summary, which is largely irrelevant now
Relevant text, under major version upgrades:
1. Check on the Drupal 8 status of your contributed and custom modules and
themes. See http://drupal.org/node/948216 for information on upgrading
contributed modules and themes. See http://drupal.org/node/895314 for a list
of modules that have been moved into core for Drupal 8, and instructions on
how to update them. See http://drupal.org/update/modules for information on
how to update your custom modules, and http://drupal.org/update/theme for
custom themes.
You may decide at this point that you cannot upgrade your site because
needed modules or themes are not ready for Drupal 8
There are a few problems with this:
1) Makes reference to http://drupal.org/node/948216 and http://drupal.org/node/895314 but these pages are only for D6 -> D7, not D7 -> D8. We need new equivalents.
2) Makes reference to http://drupal.org/update/modules and http://drupal.org/update/themes, which we don't use anymore, in favour of http://drupal.org/list-changes instead.
3) That last sentence doesn't end in a period and it DRIVES ME TO THE BRINK OF MAAAAAADNESSSSS!
:)
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | major-version-upgrade-instructions-1817020-16.patch | 5.74 KB | paulh |
| #13 | major-version-upgrade-instructions-1817020-13.patch | 5.74 KB | paulh |
| #10 | major-version-upgrade-instructions-1817020-10.patch | 6.28 KB | paulh |
Comments
Comment #1
webchickA little bit more:
...also makes reference to that link.
References to sites/*/modules and the like should probably be checked as well since in D8 the recommended practice is to use the top-level directories.
Comment #2
jhodgdonThis seems like a release blocker but not urgent for the moment. Do we have a tag for that?
Comment #3
star-szr@jhodgdon - I think this fits for #1393358: [META-12] Review 'revisit before release candidate' tag, tagging.
Comment #4
catchThis now needs all reference to major upgrades completely removed, we can mention migrate in a single sentence somewhere.
Comment #5
jhodgdon"mention migrate in a single sentence somewhere"... Um... So you mean we are not going to have a README that gives an outline of how to take a D6/7 site and migrate it to 8?!? That seems like a major omission.
Comment #6
catchWe're not going to have that until there's a release that includes migrate, no. That release may well be 8.1.x, but we need to remove references to the old major upgrade path before release. So yes eventually, but not in this issue no.
Comment #7
jhodgdonHow fun! This is most likely a good Novice issue, and a Critical. Good combination. :)
Updated issue summary to reflect what we actually want to do here.
Comment #8
paulh CreditAttribution: paulh commentedI'll give it a shot.
Comment #9
paulh CreditAttribution: paulh commentedComment #10
paulh CreditAttribution: paulh commentedOkay, doco updated and patched.
Comment #11
paulh CreditAttribution: paulh commentedComment #12
jhodgdonThanks for the patch!
Let's clean up the verb tenses here a bit. The patch says things like "will not be possible"; the fact is, it is already not possible. I also don't think we want to talk about how support for upgrade.php has been "withdrawn". Let's just document that the process for major versions is migration, in contrast to the process for minor versions, which uses update.php.
Really, we just want a sentence saying that and saying that migration support is currently only partially implemented. Don't make any references to "withdrawing" or promises for the future. Thanks!
Comment #13
paulh CreditAttribution: paulh commentedGot a bit carried away with the previous one :).
Updated as per suggestions and re-rolled the patch.
Comment #14
paulh CreditAttribution: paulh commentedComment #15
jhodgdonThis looks great to me! Except we (tradition) use American spelling/grammar in Drupal docs, so it should say "utilizing" instead of "utilising".
Comment #16
paulh CreditAttribution: paulh commentedBritish English spell checkers :). Updated and re-rolled.
Comment #17
paulh CreditAttribution: paulh commentedComment #18
jhodgdonThat looks good to me, thanks!
Comment #19
webchickI'm skipping over this one in my RTBC queue sprint because I presume jhodgdon would like to commit it. If that's wrong, let me know!
Comment #20
jhodgdonCommitted to 8.x -- thanks again all!