deadwood module

Check List for Upgrading from Drupal 5 to Drupal 6

Fri, 02/05/2010 - 6:04pm

Includes Upgrading Drupal Modules, Themes, and Site

I am a fan of check lists. They help simplify and improve the effectiveness of repetitive processes over time. The following is a recent check list I shared with a client as a summary of the process used to upgrade from Drupal 5 to Drupal 6. Please feel free to use it and add your own notes.

Together with client identify the list of key content and expected behaviors/displays. Includes any publishing/business logic.

Should be approximately 30 or so check list items, with accompanying screenshots where appropriate.
This will form the QA test script to confirm the quality of the upgrade and will be the list for acceptance testing.

Duplicate the site, code, db, and files into an upgrade branch on dev server.
Version control all code, db, view exports, ect. throughout the process
Confirm there are no custom hacks on Drupal core.
Run the upgrade process for Drupal Core.
Test

All steps titled test include some automated testing as well as use of the coder module.
I also just came across the deadwood module.
Test steps also include running through the QA test script when appropriate.
See links below.

Run the upgrade process on views, converting views to views 2
Test
Identify any custom hacks on contrib. modules.
Upgrade contrib. modules which have D6 versions
Test
Identify upgrade paths for non standard modules and those which do not have a d6 version
Code the upgrades and run them
Test (full developer review)
Client QA and site review/Bug fixing Cycle
Prepare deploy plan
Deploy the upgrade on production server
Client QA and site review/Server Configuration and Bug fixing Cycle
Client Acceptance testing (walking through the script), reporting and fixing issues cycle