[webkit-qt] Proposal: Qt 4 removal from trunk, Qt 5 changes

Caio Marcelo de Oliveira Filho caio.oliveira at openbossa.org
Mon May 28 14:13:23 PDT 2012


>> What exactly is involved in maintaining it in the trunk itself ? Would such
>> maintenance require more than one person ?  I just do not see how the
>> out-of-trunk maintenance is supposed to work.
> In-trunk maintenance requires keeping a bot green and regularly catching up
> with changes that happen in WebKit. If we just keep the Qt 4 code in trunk and
> let it "rot" then for a while people will continue to blindly change the Qt 4
> files if they do internal API changes, but that'll stop sooner than later. Then
> the code becomes bitrot and it looks bad.
> An out-of-trunk maintenance requires probably more effort in merging itself,
> but it's completely up to the people maintaining it _when_ they choose to do
> it and how long it'll take them.

I think these are good arguments to remove Qt4 support from trunk.

However, it's still unclear to me whether this thread reached a
conclusion or not.


Caio Marcelo de Oliveira Filho
openBossa @ INdT - Instituto Nokia de Tecnologia

More information about the webkit-qt mailing list