On 29.5.2012 0.13, "Caio Marcelo de Oliveira Filho" <caio.olive...@openbossa.org> wrote:
>Hello, > >>> 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. > I do not think the final verdict was given by Simon on this one. As I said in my earlier mail, I really would like to see 4.8 webkit updated as soon as Qt 5.0.0 is out. In order to do this, I would like to keep things running in the Qt Project systems. Currently it seems that after 5.0.0 we can provide some help into this. And it is great that there are also others in the community who have expressed interest. If it is possible to do this together, it is easier to succeed. Yours, -- Tuukka Turunen Director, Qt Commercial R&D Digia Plc Piippukatu 11, 40100 Jyväskylä, Finland Visit us at: www.digia.com or qt.digia.com _______________________________________________ webkit-qt mailing list webkit-qt@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
