Yes, we're working feverishly (is that a good word for this? :) to
make this situation a bit less hard.
However, in the meantime, the process could go like this:
1) Make sure the canary had a green run. This would really help the
WebKit gardener to know which revision to roll up to.
2) Land you
I suspect there are things we can do that will avoid much of the need to do
a Chromium side change in unison with a WebKit side change. #1 is probably
upstreaming some .gypi files so that the set of files to build can be stored
in svn.webkit.org. The WebKit API will also help, and completing the
