[webkit-qt] Conclusion (was RE: Proposal: Qt 4 removal from trunk, Qt 5 changes)
simon.hausmann at nokia.com
simon.hausmann at nokia.com
Sat Jun 2 00:02:40 PDT 2012
Let's target week 24 or week 25 for the Qt 4 removal from trunk. I've filed https://bugs.webkit.org/show_bug.cgi?id=88161
Now's a good time for last minute objections :)
Simon (OOO in W23)
From: ext andrea diamantini [adjam7 at gmail.com]
Sent: Friday, June 01, 2012 18:34
To: Hausmann Simon (Nokia-MP/Oslo)
Cc: ext Turunen Tuukka; Caio Marcelo de Oliveira Filho; webkit-qt at lists.webkit.org
Subject: Re: [webkit-qt] Proposal: Qt 4 removal from trunk, Qt 5 changes
I'm ok Simon.
Unfortunately, I'm having problems at work and I cannot start seriously working on qtwebkit until the end of June. But plans are confirmed. I'll branch out definitely from the last commit before qt4 removal, starting from there the stabilization process.
2012/6/1 Simon Hausmann <simon.hausmann at nokia.com<mailto:simon.hausmann at nokia.com>>
On Tuesday, May 29, 2012 05:27:45 AM ext Turunen Tuukka wrote:
> On 29.5.2012 0.13, "Caio Marcelo de Oliveira Filho"
> <caio.oliveira at openbossa.org<mailto:caio.oliveira at openbossa.org>> wrote:
> >>> What exactly is involved in maintaining it in the trunk itself ? Would
> >>> 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
> >> 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.
I would love to proceed as long as the people who are interested in an out-of-
trunk Qt 4 port are okay with it, i.e. they have a rough idea about the
implications and would not be totally upset if we did this.
> 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.
It's great to hear that you are interested in this and would be willing to
Perhaps this is enough for us to proceed? I can try to help with the merging
Andrea, are you okay with it as well?
More information about the webkit-qt