Chrome Git migration is not happening this Friday, new date is TBD

36 views

Skip to first unread message

Chase Phillips

unread,

Apr 23, 2014, 8:18:04 PM4/23/14

to Chromium-dev, blin...@chromium.org

Hi everyone,

We have not completed key goals for the Chrome Git switch so flag day will not happen on April 25th or May 2nd. We will pick a flag day when we complete these open items:

Web-based Git blame usability:

Based on your feedback we realized that there were still areas of blame to be improved. Since the previous thread, we improved web-based Git blame performance and usability. Here are some examples:

The default blame view has been updated to show diff by default and will be live as soon as tomorrow. Meanwhile, details of progress are discussed here.
Speed improvements have been made that have optimized the blame view algorithm. This should result in faster cold loads for some blamed files. For example:

https://chromium.googlesource.com/chromium/src/+blame/master/content/renderer/render_view_impl.cc took 22s to load, where before others were seeing 2+ mins of load time.

Improved caching has improved the performance of blame loads. To test this out, fetch blame of a random file in googlesource.com and then re-fetch blame. For example:

https://chromium.googlesource.com/chromium/src/+blame/master/content/renderer/render_view_impl.cc took 22s to load the first time, took ~2s to load the second time, etc.
https://chromium.googlesource.com/chromium/src/+blame/310ebd630b77e0f3883647ebcf7458b2010f0a51/content/renderer/render_view_impl.cc took 10s to load the first time, took ~5s to load the second time, etc.

Revision numbers:

Prior to last week, we expected the Git workflow/tools to be sufficient for the team. However, we continue to receive feedback from those that rely on SVN revision numbers. We are weighing possible solutions to this problem.

Finally, before flag day, all bots need to use a Git checkout and some docs are left to write. Expect another update once we complete this work. Thanks!