[webkit-qt] For WebKit2 developers - newer Qt5, bug fixing

Alexis Menard alexis.menard at openbossa.org
Tue Oct 4 08:30:55 PDT 2011


On Tue, Oct 4, 2011 at 10:18 AM, Jarred Nicholls <jarred at sencha.com> wrote:
> On Tue, Oct 4, 2011 at 7:18 AM, Alexis Menard <alexis.menard at openbossa.org>
> wrote:
>>
>> On 30/09/2011, at 04:43, Osztrogonac Csaba <oszi at inf.u-szeged.hu> wrote:
>>
>> > Dear QtWebKittens,
>>
>> Yo
>>
>> >
>> > Yesterday evening we made the "x86-32 Linux Qt Release WebKit2" buildbot
>> > on
>> > http://build.webkit.sed.hu/waterfall?category=core use newer Qt5
>> > revision
>> > (revision after Qt5 refactoring)
>> >
>> > And then Tor Arne landed a buildfix for WebKit trunk:
>> > http://trac.webkit.org/changeset/96345
>> >
>> > Unfortunately with newer Qt there are 10605 new failing test. It is a
>> > _very very big_ number,
>> > approximately half of the tests. I skipped all of them not to kill the
>> > buildbot master.
>> > (Skip tests: http://trac.webkit.org/changeset/96355)
>> >
>> > But we should stop for a minute in this crazy developing race and make
>> > allowance for QA.
>>
>> The crazy development race is more on Qt5 than WebKit. With the big beast
>> landed in Qt5 it's more little things that should be changed in the future.
>> For now since this merge we were just firefighting (build fixes, event
>> delivery broken, ...). So yes we are trying to fix :). In the other hand
>> with Qt5 new and QtWebKit2 don't expect high quality QA for now as we need
>> to get major architectural changes in, API refactor, ... When Qt5 will enter
>> in stabilization phase we can do so and then we can all focus on QA to get
>> it in shape for a release.
>>
>> > I filed a meta bug: https://bugs.webkit.org/show_bug.cgi?id=69104 . It
>> > would be great
>> > if we can fix these regressions _as soon as possible_ to hit the test
>> > coverage before
>> > Qt5 refactoring.
>>
>> I haven't give a try myself as I work on my dev days presentation but
>> what's wrong with those tests? Do you have an idea? With WebKit1 slowly
>> phasing away we should all focus on WebKit2, WebKit1 trunk is something
>> nobody uses.
>
> I beg to differ - though for all intents in purposes...you're right ;)

Well at least Nokia will probably not release anything on top of
WebKit1 trunk. And so far nobody stepped up to take over the
maintenance.

>
>>
>> >
>> > br,
>> > Ossy
>> > _______________________________________________
>> > webkit-qt mailing list
>> > webkit-qt at lists.webkit.org
>> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>> _______________________________________________
>> webkit-qt mailing list
>> webkit-qt at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>
>
>
> --
> ................................................................
> Sencha
> Jarred Nicholls, Senior Software Architect
> @jarrednicholls
>
>



-- 
Alexis Menard (darktears)
Software Engineer
INdT Recife Brazil


More information about the webkit-qt mailing list