On Wednesday, June 06, 2012 09:37:14 AM ext Allan Sandfeld Jensen wrote: > On Wednesday 06 June 2012, [email protected] wrote: > > Hm, okay, maybe we can improve the timing :) > > > > What would be the advantage of waiting until Qt 5.0 is released? What > > would > > be different at that point? > > By branching of the same version as Qt 5.0 it will hopefully benifit from > the stabilization up to Qt 5.0, plus it means we can hopefully keep the > QtWebKit for Qt 4.x version close to the branch used for Qt 5.0, which > means we can possible merge similar patches, etc. > > From an communication POV it is also simpler to explain that this fork will > provide the features available in QtWebKit for Qt 5.0 to Qt 4.x (except > WebKit2 of course).
I think that is a really good point, a new Qt 4 based QtWebKit 2.3 release should have the same (WebCore) feature set as WebKit in Qt 5. I really like that. But that doesn't require us to branch at the same time, does it? If we removed Qt 4 support from trunk today and create a out-of-trunk Qt 4 branch, we'd still merge WebKit trunk (and thus WebCore features) up until the point where we would also branch off for Qt 5 and stop merging from trunk. Simon _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
