Problem/Motivation
This handbook page describes how to update a D8 site to D9:
https://www.drupal.org/docs/9/how-to-prepare-your-drupal-7-or-8-site-for...
It should be generalized to describe D8+ updates in general, so that it also covers D10 updates.
Proposed resolution
The Upgrading from Drupal 8 (or later) wiki is now has the following pages/guides
- Upgrading a Composer-based site - generic instructions
- Upgrading from Drupal 8 to Drupal 9 - the original pages
- Upgrading from Drupal 9 to Drupal 10 - new page for any special information for Drupal 10
Update.txt is being done in #3266004: Update UPDATE.txt for Drupal 10
Remaining tasks
Review
Comments
Comment #2
quietone commentedThis page is in the guide How to prepare your Drupal 7 or 8 site for Drupal 9 which is .. odd.
There is also this page which seems to be doing the same thing, Upgrading from Drupal 8 to Drupal 9 (or later)
I was going to make some suggestions to unify these pages but I just ran out of steam.
Comment #3
xjmYeah I noticed #2 today as well. There should be subsections for each type of major version update, rather than lumping them all together. I think the whole guide needs to be restructured.
Comment #4
quietone commentedRight now we have this structure, abbreviate of course. The 'Upgrading Drupal' section is primarily migrate related except for the ** page.
We could rename 'Updating Drupal' to Updating Drupal 8+' and rename 'Upgrading Drupal' 'Updating from Drupal 6 or Drupal 7 to Drupal 8+' and move the '**' page to the 'Updating Drupal 8+' section. I think that will guide people to the information they need and not mix the two up.
Comment #5
gábor hojtsyHistorically we used updating to mean updating within the same major while upgrading meant moving up a major or two. Are we now to use updating regardless of versions? I think that is one thing we need to agree on to make sure we structure it in a forward looking way.
Comment #6
quietone commentedThe Upgrading Drupal guide contains guides for upgrading from D6/D7 and from D8, D9. The two should be separated.
Change this
To
Personally, I like the distinction of upgrade/update as stated in #5 but I don't mind it that changes. I am far more concerned that the structure of the documentation here is unhelpful.
Comment #7
quietone commentedI've done a bit of re-ordering at Upgrading Drupal and made new page for 'Upgrading from Drupal 9 to Drupal 10'. I thought a new page was needed so that there is place to mention things to watch out for that are unique to Drupal 9 to 10. The new page uses the Overview from Upgrading from Drupal 8 to Drupal 9 as a start. It definitely needs links to the correct composer instructions.
That doesn't meet the goal in the IS of having a generic page but maybe that is OK?
Comment #8
quietone commentedThe new structure is:
Upgrading from Drupal 8 (or later)
-- Upgrading from Drupal 8 to Drupal 9
-- Upgrading from Drupal 9 to Drupal 10
Comment #9
quietone commentedAdded generic instructions.
And the guides "Upgrading Drupal" and "Updating Drupal" are now next to each other on the Drupal wiki. I am hoping that will help the readers. I think eojthebrave did that. Thanks!
The pages are ready for review.
Comment #10
smustgrave commentedReviewing the pages and they look fine to me. D10 being out a few months if they were really bad think someone would of said something by now.
Though I think it may be worth adding something for taking over abandoned modules. People are quickly realizing that modules they use are abandoned or lacking support.
Comment #11
quietone commentedTherefor, I am changing back to a task.
The suggestion in #10 is a change of scope. This issue is specifically about generalizing a set of pages, not adding more data. Changing back to NR.
I'll talk to @smustgrave in #needs-review-queue about the suggestion in #10.
Comment #12
smustgrave commented@quietone did bring it up and I was coming at it with more of a developer mindset so needing the ability to take over a module and update the code for D10 would be out of the realm of an upgrader.
Comment #13
catchThis all looks fine to me, marking fixed. Wonder if it should have been against https://www.drupal.org/project/issues/documentation