On 01/02/2017 04:50 PM, Phil Bouchard wrote:
On 12/29/2016 04:14 AM, Simon Hausmann wrote:
Hi,
Sorry for the delay...
First I would like to point out this popular Javascript test runs 1.5
faster using Qt over WebKit:
- ~100 FPS on my laptop (x86 @ 2.40GHz) using Chrome (WebKit):
http://www.t
On tirsdag 3. januar 2017 08.02.21 CET Tuukka Turunen wrote:
> Hi,
>
> Perhaps it is best to talk with marketing about the name of the "release
> done immediately after branching to the .0 release branch". Reading the
> discussion, it seems that other than the name we are well aligned.
I'd try to
Since general churn while "stabilising" is a central part of the
discussion, let's take a look at the change, since my early November API
review push, in just the not-obviously-boring[*] changes to API-related
headers. ([*] If you can see any changes in the reviews that a dumb
script could be taugh
Back on the 7th of November 2016 I announced:
> With the 5.8.0 release now close at hand, I've updated the API reviews:
I've now updated these for the actual 5.8.0 branch (fetched this morning):
https://codereview.qt-project.org/170634 - qtbase
https://codereview.qt-project.org/170635 - qtdeclara
Hi,
as a result of the QtCon 2016 discussion on Managing Qt's Branches (
http://wiki.qt.io/QtCS2016_Managing_Qt_Branches ), we would like to
provide some guidelines on which branch to choose for a change. Please
find attached a QUIP which is available for review at
https://codereview.qt-proje
Hi,
As someone living quite close to marketing.
A couple of questions.
1. As the T-4 release is essentially from the start of the 5.n.0 branch,
are only fixes allowed there? (no new content, unless for some really weird
reason)
2. Is it possible that the T-4 release could be so go
