News for hackers. Stuff that matters.

A comment on Blink: A rendering engine for the Chromium project. Parent comment

Re:Blink: A rendering engine for the Chromium project by mikewest on Wednesday April 03, 2013 @06:39PM (#5489745)
WebKit and Chromium are different repositories, and point to each other via a "DEPS" (dependencies) file. We roll new revisions of WebKit into Chromium regularly, and call the process of diagnosing and fixing problems with the rolls "Gardening": http://www.chromium.org/developers/how-tos/webkit-gardening is a good reference.
[ Parent | on HN ]
Re:Blink: A rendering engine for the Chromium project by tripzilch on Thursday April 04, 2013 @04:34AM (#5491602)
Hey, clicking around that Wiki it has some pretty interesting information. Do other large open-source projects have a very similar workflow?
[ Parent | on HN ]
Re:Blink: A rendering engine for the Chromium project by zanny on Thursday April 04, 2013 @06:34AM (#5491860)
You mean having full-time engineers handling merge conflicts / upstream breakage / regressions / running test suites? In anything sufficiently large, that becomes a major issue inevitably.

Almost any project worth its salt has someone doing testing. But it is really time consuming.

[ Parent | on HN ]
Re:Blink: A rendering engine for the Chromium project by bradleyjg on Thursday April 04, 2013 @07:06AM (#5491944)
The most significant long term upstream-downstream relationships are probably the linux distros to the kernel.
[ Parent | on HN ]