My quick opinion on it is that we could: - Switch the official bots to Qt5 as soon as possible to aid the Qt5 beta - Branch Qt4 at the same time as Qt5 (two different branches would be better I guess) - Remove the Qt4 code from trunk (that might be broken already since the bots won't be running) once we stabilized the Qt5 branch
br, Jocelyn On Wed, 6 Jun 2012 09:37:14 +0200 ext Allan Sandfeld Jensen <k...@carewolf.com> wrote: > On Wednesday 06 June 2012, simon.hausm...@nokia.com 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). > > > `Allan > _______________________________________________ > webkit-qt mailing list > webkit-qt@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt _______________________________________________ webkit-qt mailing list webkit-qt@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
