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
UPDATE.txt tells users how to update from Drupal 8 to Drupal 9. We need to update this before release of Drupal 10.
Steps to reproduce
Proposed resolution
Replace references to Drupal 9 with Drupal 10, and then references to Drupal 8 with Drupal 9.
Add a section about updating from Drupal 8 to Drupal 10.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#15 | 3266004-15.patch | 2.67 KB | quietone |
#15 | interdiff-11-15.txt | 635 bytes | quietone |
#11 | 3266004-11.patch | 2.67 KB | quietone |
#11 | interdiff-9-11.txt | 1.64 KB | quietone |
#9 | 3266004-9.patch | 2.35 KB | quietone |
Issue fork drupal-3266004
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
longwaveComment #3
beatrizrodriguesComment #4
beatrizrodriguesComment #6
Gábor HojtsyThis sounded like it would be easy to do, but in fact it depends on #3271874: Update handbook guide for updating to D9 to be generalized for D10 and future major updates first to be doable I think. So marking postponed.
Comment #7
quietone CreditAttribution: quietone at PreviousNext commentedI've made a few changes to the documentation so I've started to update this. I made a patch to avoid running tests.
Comment #8
longwaveTagging as a stable release blocker, as ideally we should not ship with out of date docs.
Comment #9
quietone CreditAttribution: quietone at PreviousNext commentedRemove some instances of 'Drupal 10'.
While the new doc page still needs work I think this can be reviewed, so changing status.
Comment #10
longwaveDo we want to retain a "Updating Drupal 8" section given that we have sections for 6, 7 and 9? Drupal 6 is also EOL, but I think there are more likely to be Drupal 8 users reading this than Drupal 6 users.
This might want to say "earlier" instead of "previous"?
Comment #11
quietone CreditAttribution: quietone at PreviousNext commentedThanks. I added it back and checked all the links.
Comment #12
urvashi_vora CreditAttribution: urvashi_vora at Valuebound for Valuebound commentedHi @quietone,
I reviewed the changes in the patch. It looks good to me. Moving it to RTBc.
Thanks for the patch.
Comment #13
quietone CreditAttribution: quietone at PreviousNext commented@urvashi_vora, thanks for the interest. It is not clear to me what you did to determine that this 'looks good'.
I am setting this back to NR for someone to check all the links.
Comment #14
longwave"or" should be "to"
"OR" should perhaps be "or" to be consistent with the other titles (or, capitalise all the titles)
Comment #15
quietone CreditAttribution: quietone at PreviousNext commentedThanks again.
This should fix everything in #14. The titles are all in caps now.
Comment #16
longwaveThanks. I patched the file locally and read through the whole thing and it all makes sense to me. I also checked each of the links and they all work and go to the expected page in the documentation, containing next steps for each option. We can further improve the online documentation as we go along but to me this is good for the initial pointers in UPDATE.txt.
Comment #18
catchThis looks good. Agreed with keeping the 8-9 upgrade section, there's still tens of thousands of sites running 8.x that need to get onto 9. Technically that section would still be in the Drupal 9 code base, but you never know where people will look.
Committed/pushed to 10.1.x and cherry-picked to 10.0.x, thanks!