Problem/Motivation
The test bot can do upgrade tests but manual upgrade tests more OSes , PHP versions, special circumstances and who knows what else. Update is extremely finicky.
The bot is useful and the tests are very good keeping it mostly sane.
The testbot can't test rewriting settings.php
Proposed resolution
Get people to regularly test the upgrade.
We need it tested on:
- Windows - last tested: never?
- Linux - last tested: ?
- Mac - last tested: ?
- (list others)
Remaining tasks
- (ongoing) test, make a comment retest once every two weeks or so. make a comment on this issue saying "I tested on X OS, with php version A.B.C and the result is: [it worked|it blew up with Z error]." (Why? Making a comment saying it was tested helps us know testing is being done and stuff is working ok.)
- (ongoing) update summary update the issue summary near the OS saying: last tested M D Y [ok|broken] #XX, for example near Windows: last tested March 30 2013 [ok] #11. (Why? That way we know more info is in comment #11 about that test. And people can easily see what has been the longest since it was tested.)
- (ongoing) create follow-up issues File individual issues for problems found, and link them from here. Tag them with: D8 upgrade path (Why? because this would get overloaded if we fixed the problems here.) Docs on making good issues: Issue summary: http://drupal.org/node/1427826 and Steps to reproduce http://drupal.org/node/1468198
Steps to test
- install d7
- create a node or two
- upgrade to d8
User interface changes
no changes. this is a meta.
API changes
no changes. this is a meta.
Related
- #1919002: Upgrade to D8 broken when D7 has more then one language enabled
- #1943726: BootstrapConfigStorageFactory and update
See also for perspective:
http://drupal.org/project/issues/search/drupal?issue_tags=D7+upgrade+path