On Sunday, June 13, 2010 08:14:44 pm Kling Andreas (Nokia-D/Oslo) wrote: > 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?
I think the Qt 4.7 program would not accept any new features at this point. The main blocking issue I can see right now for the release is the memory usage that is too high and in particular on low-memory Symbian devices causes crashes. On the other hand this issue doesn't fix itself, so maybe we should set up a team/task force to look for quick wins in terms of the memory usage. Simon _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
