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

Issue fork drupal-3266004

Command icon 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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

longwave created an issue. See original summary.

longwave’s picture

Component: base system » documentation
beatrizrodrigues’s picture

Assigned: Unassigned » beatrizrodrigues
beatrizrodrigues’s picture

Assigned: beatrizrodrigues » Unassigned

Gábor Hojtsy’s picture

Status: Active » Postponed

This 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.

quietone’s picture

FileSize
2.43 KB

I've made a few changes to the documentation so I've started to update this. I made a patch to avoid running tests.

longwave’s picture

Tagging as a stable release blocker, as ideally we should not ship with out of date docs.

quietone’s picture

Remove some instances of 'Drupal 10'.

While the new doc page still needs work I think this can be reviewed, so changing status.

longwave’s picture

Do 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.

+++ b/core/UPDATE.txt
@@ -46,32 +46,27 @@ UPDATING CODE WITH COMPOSER
  * Updating from a previous major version, such as Drupal 6 or 7, requires

This might want to say "earlier" instead of "previous"?

quietone’s picture

FileSize
1.64 KB
2.67 KB

Thanks. I added it back and checked all the links.

urvashi_vora’s picture

Status: Needs review » Reviewed & tested by the community

Hi @quietone,

I reviewed the changes in the patch. It looks good to me. Moving it to RTBc.

Thanks for the patch.

quietone’s picture

Status: Reviewed & tested by the community » Needs review

@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.

longwave’s picture

Status: Needs review » Needs work
  1. +++ b/core/UPDATE.txt
    @@ -46,32 +47,34 @@ UPDATING CODE WITH COMPOSER
    +UPDATING DRUPAL 8 or DRUPAL 9
    

    "or" should be "to"

  2. +++ b/core/UPDATE.txt
    @@ -46,32 +47,34 @@ UPDATING CODE WITH COMPOSER
    +UPDATING DRUPAL 6 OR DRUPAL 7
    

    "OR" should perhaps be "or" to be consistent with the other titles (or, capitalise all the titles)

quietone’s picture

Status: Needs work » Needs review
FileSize
635 bytes
2.67 KB

Thanks again.

This should fix everything in #14. The titles are all in caps now.

longwave’s picture

Status: Needs review » Reviewed & tested by the community

Thanks. 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.

  • catch committed 185fa5e on 10.0.x
    Issue #3266004 by quietone, longwave: Update UPDATE.txt for Drupal 10
    
    (...
  • catch committed a134173 on 10.1.x
    Issue #3266004 by quietone, longwave: Update UPDATE.txt for Drupal 10
    
catch’s picture

Status: Reviewed & tested by the community » Fixed

This 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!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.