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
_______________________________________________
webkit-qt mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
