[webkit-qt] QtWebKit trunk development after 5.0 release - questions

Simon Hausmann simon.hausmann at digia.com
Thu Jan 24 03:47:12 PST 2013

On Monday, January 21, 2013 05:28:31 PM Jocelyn Turcotte wrote:
> On Mon, Jan 21, 2013 at 05:02:53PM +0100, Osztrogonac Csaba wrote:
> > Hi All,
> > 
> > Qt 5.0 was released a month ago. And I have two major questions
> > about the future of the QtWebKit trunk (svn.webkit.org) development.
> > 
> > Question no 1:
> > ---------------
> No objection from me.

Sounds good to me, too.
> > Question no 2:
> > ---------------
> > 
> > Which Qt version / revision should we use for WebKit trunk?
> > 
> > We always use build-qt5.sh script to build Qt for WebKit trunk to reduce
> > source incompatible changes and make it simple to have same environment
> > to reproduce bugs, etc. ( https://github.com/ossy-szeged/qt5-tools )
> > 
> > But now we are pinned on a very old, pre Qt 5.0 revision:
> > 8d77ff1ef2422259dd6baed5cae9815260e5bee2 (Tue Dec 4 11:54:27 2012 +0100)
> > 
> > I think it's time to update Qt on the bots/developers machines.
> > So the question is which Qt revision should we update to?
> > - Qt 5.0.0 release version? (I tested it on Linux, and works fine)
> > - Or trunk qt5.git? (I haven't tested it yet.)
> > 
> > And then should we do regular weekly/mothly update again?
> > Or should we do updates on demand only?
> At this point we can start having a stabilisation process like we had for
> Qt4. Basically trunk should always build with the last one or two stable
> releases (5.0.x in this case) and features that need new
> qtbase/qtdeclarative APIs should be protected by Qt version check macros.
> I'm not sure if we need a bot to cover features depending on trunk qt5.git,
> but I think that the bot should at least run the latest 5.0.x Qt release to
> catch regression introduced by QtWebKit rather than the rest of Qt.

I suggest the bots should run the last stable release of Qt 5, i.e. Qt 5.0.x 
at this point.

If during WebKit development we need features from the current development 
version of Qt (i.e. the "dev" branch), then the code using these features 
should indeed be #ifdef'ed appropriately to support continued building and 
running with the latest stable release of Qt.

If it turns out that we really need the latest dev branch of Qt 5 also for the 
bots for testing, then I suggest we decide on a case-by-case basis here, 
because it comes at a significant "cost" for bot maintenance as well as the 
development community.


More information about the webkit-qt mailing list