-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D10 Upgrade - Forest Legality (HOLD) #288
Comments
@katieescoto @monicapatel21 What repo is this? I was able to find the URL https://forestlegality.org/ but have had no luck tracking down an associated git repo. |
@komejo the repo is only in Pantheon! No github repo for this one. |
@katieescoto Whoa! So no Composer or Robo either I take it? I saw the Pantheon account with all of the upstream updates, I'm guessing those'll disappear after I upgrade it to D10? |
@katieescoto there is some confusion with the old vendor on handling this work -- have you started? If not we can hand off to them |
@StudioZut We haven't started yet, please feel free to hand this over. |
Great, thanks, we'll hand this to them (DarwinApps) and move this to the Backlog for now |
Dev [8hrs]
This site's "Upgrade document"
https://docs.google.com/spreadsheets/d/1wgTNEzYh6FW4N5o_Jy_hwXSMmhWW5vepeTXmLPNL0NQ/edit?usp=sharing
Maintenance page
-- place maintenance screenshot here --
Working Branch
-- place the working branch here --
Estimate for phase 2
-- place the estimate for upgrading the site here --
Update Branch
-- add update branch here --
Part 1: Prep
At the end of this work, the site be in a state closer to be ready for a Drupal 10 update. Some of its modules may have been updated. There will be a spreadsheet (the "Upgrade document") with accurate information about how much time the upgrade should take.
Step 1 - organization things:
terminus drush YOURSITE.live -- pml --format=csv --no-core > YOURSITE.csv
. You can then upload that list to the google drive "Upgrade document" you made in the last step, and alter the columns as needed. Note: Sometimes this command times out on the live site. You can try running it without the>
and just copy/paste the output into a csv file if this happens. Then upload the csv to the Upgrade Document with "Append to the current sheet"Step 2 - cleaning up the code:
robo install
to make sure everything's clean on your local.composer remove xx/xx
any modules in the "Upgrade document" where the status is "Removed from the site".sphp 8.1
)thinkshout/robo-drupal
requirement is atv4.0.0
or higher.composer require --dev "thinkshout/robo-drupal:^4.0.0"
composer require --dev drupal/upgrade_status && drush en upgrade_status
.Step 3 - finalizing the update list:
/admin/reports/upgrade-status
page, note any modules in the "UPDATE" and "COLLABORATE WITH MAINTAINERS". Indicate the module status in the "Upgrade document".Step 4 - Estimating
Note that if you know your custom code is complicated, you can up the amount of time as you see fit.
Part 2: Update
Dev [Xhrs]
Deployment 2: Upgrade
Step 1 - Maintenance page approval
Step 2 - Code updates
/admin/reports/upgrade-status
, update each modules listed under "UPDATE" using something likecomposer update drupal/modulename --with-dependencies
./admin/reports/upgrade-status
, look at the modules remaining under "UPDATE" and "COLLABORATE WITH MAINTAINERS" and see which modules need a major version upgrade. Handle those with something likecomposer require drupal/modulename -W
./admin/reports/upgrade-status
, look at what's left under "UPDATE" and "COLLABORATE WITH MAINTAINERS" and check all issue pages for these on drupal.org to see if there's a D10 patch available. If any modules do not have a D10 update or patch, note them below under "List modules that do not have a D10 compatible version of patch available." These might be good to discuss with other devs to see how to best approach these.drush updb
anddrush cex
/admin/reports/upgrade-status
and drupal-check, do the Drupal 10 upgrade. Run this commandcomposer require drupal/core-recommended
. This should update you to the latest version of drupal core on the 10.x branch. Note: If you still run into conflicts, try removing everything in your dev dependencies before running the update command. Don't forget to add everything back once the upgrade is successful.Step 3 - Finalize testing instructions
Notes
Testing Instructions:
Deployment steps
test
multidev (not develop) using a recent copy of the live site's database, a day before the go-live deploy. You should also run any VR tests comparing test and live at this time.drush cr
,drush updb
until there are no more pending updates. It might take a few tries to get them all.drush cim
.Followup items:
This Ticket is Done When:
The text was updated successfully, but these errors were encountered: