[webkit-qt] Rebasing QtWebKit 2.0 on current trunk?

[siddharth.mathur at nokia.com]

As a developer who often has to do root cause analysis of performance issues of QtWebkit-Symbian based products (and potentially upstream patches or file bugs), I would find it desirable if were in synch with trunk as much as humanely possible. It will save a lot of effort after QtWebkit 2.0 is released, and in active use by products. In other words, more confidence in explaining why it's behaving the way it is. 

It's a beast. :)

Siddharth



From: webkit-qt-bounces at lists.webkit.org [mailto:webkit-qt-bounces at lists.webkit.org] On Behalf Of Kling Andreas (Nokia-D/Oslo)
Sent: Sunday, June 13, 2010 2:15 PM
To: webkit-qt at lists.webkit.org
Subject: [webkit-qt] Rebasing QtWebKit 2.0 on current trunk?

Given the currently slipping schedules, should we perhaps consider rebasing QtWebKit 2.0 on current WebKit trunk?

Apple pushed some nice speed and memory improvements before releasing Safari 5 and these could really benefit us, not to mention the 4 months of "regular" work that WebKit has had since we originally branched off.

Some examples:

https://bugs.webkit.org/show_bug.cgi?id=35850
https://bugs.webkit.org/show_bug.cgi?id=38682
https://bugs.webkit.org/show_bug.cgi?id=39035
https://bugs.webkit.org/show_bug.cgi?id=39171
https://bugs.webkit.org/show_bug.cgi?id=39180
https://trac.webkit.org/changeset/59281
https://trac.webkit.org/changeset/60392

Yes, we could obviously cherry-pick these changes, but given the current timeframe, I personally think that rebasing (and re-entering stabilization mode) could be worthwhile.

Thoughts?

Kling