Affects Version/s: 2.0
Fix Version/s: 2.0
Versioning Impact:Patch (backwards-compatible bug fixes)
We want to manually test a handful of upgrade scenarios:
|Designation||CRM start||CRM end||Vol start||Vol end||Rationale||Results|
|A||4.6.11||4.6.11||1.4.1||2.0||Upgrade last 4.6-compatible version of vol to latest||No Issues Found|
|B||4.6.11||4.7.0||2.0||2.0||Ensure 2.0 instances running in 4.6 don't break when the CRM is upgraded||Blank Manage Volunteers Screen , Handed Off to Frank|
|C||4.7.0||-||2.0||-||Not actually an upgrade; haven't had as much user testing in 4.7 as 4.6||Logged
|D||4.4.20||4.6.11||1.3.2||2.0||Ensure LTS support. Order of upgrades: first CRM, then Vol||Blank Manage Volunteers Screen , Handed Off to Frank, Also found
Civix will be your friend here for setting up environments on the quick. To properly test some of the upgrade steps, it will be necessary to create some test data (e.g., test projects, test needs, test assignments).
You may find it helpful to turn on debugging, but any errors that occur will appear in CiviCRM's log. If you encounter any problems, please create new tickets with as much detail as possible – minimally the log output – and link them to this issue.
All tests performed with Drupal 4.7 using drupal-demo as the installation option with BuildKit.