[webkit-qt] Conclusion (was RE: Proposal: Qt 4 removal from trunk, Qt 5 changes)

[Allan Sandfeld Jensen]

That could be a solution. Though, if it is not too much trouble, I would 
suggest keeping the Qt4 build-bot, but still switch the test-bots to Qt5-only 
to focus infra and QA resources. Hopefully supporting a build bot wouldn't be 
too much trouble and would catch any misplaced Qt5-only code.

BR
`Allan 

On Wednesday 06 June 2012, Jocelyn Turcotte wrote:
> 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 <kde at carewolf.com> wrote:
> > On Wednesday 06 June 2012, simon.hausmann at 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 at lists.webkit.org
> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt