I wanted to say thanks to tkent@ for doing so much work with the move plan script recently ( bug 578345 ).
So I expect that when the actual rename happens, the issues that we hit will be similar to those hit with the Blink Rename.
What is required of the "rebase tool" for this? What is the rebase tool for the Blink Rename like?
Also, without tkent@ driving this in Q4, if nobody else volunteers, I'm assuming this will wait until 2018? But it might still be possible to move Tools/Scripts before Source/.
PS Great lightning talks about both the Blink Rename retrospective as well as this plan!
Related to tools/scripts moving: another thing to potentially rename at some point (not necessary for the main move) is "run-webkit-tests". If LayoutTests is being renamed to web_tests (announced at BlinkOn lightning talk) then one possible name would be run-web-tests.
Re comment 22: Since this is a lot more automatable than the Rename, I hope this will be more similar to the Great Reformat, not the Great Rename. In particular, rebasing should be hopefully be completely transparent like it was with the Reformat.
What issues in particular are you thinking of?
Re #30: I'm not sure myself what issues there may be ... I added that comment after tkent's status update at BlinkOn which noted that building Chrome now works after moving with the move script that tkent wrote (https://chromium.googlesource.com/chromium/src.git/+/master/third_party/blink/tools/move_blink_source.py), but there's no rebase tool.
I was hoping that people who know better (e.g. you, dcheng) could advise about potential pitfalls based on past experience.
Comment 1 by tkent@chromium.org
, Jul 11 2016