Re: [Development] [Qt-creator] Nomating Przemyslaw Gorszkowski as approver

On Fri, 30. Jan 11:00, Orgad Shaneh wrote: > I'd like to nominate Przemyslaw as approver. > ... > He resolved some of the most annoying bugs, and handled many complicated > use-cases. He also monitors the bugtracker and asks where he can help out. +1! Nikolai __

Re: [Development] CI configuration changes

Hi Here's a wiki page describing the planned changed along with a bit of version information of the tools: http://qt-project.org/wiki/Qt-5.5.0-tools-and-versions -Tony > -Original Message- > From: development-bounces+tony.sarajarvi=theqtcompany.com@qt- > project.org [mailto:development

Re: [Development] Feature freeze approaching

On Thursday 29 January 2015 10:02:57 Knoll Lars wrote: > Hi everybody, > > Just a short reminder to you all that the feature freeze and branching of > Qt 5.5 is approaching. The current plan is to branch 5.5 on the 9th of > February. > > If you have any feature that should really go in and still

[Development] New Qt 4.8.7 snapshot build is available

Hi, New Qt 4.8.7 snapshot build is available http://download.qt.io/snapshots/qt/4.8/4.8.7/2015-02-02-3/ Snapshot is built against sha1 8960f7356796948b161159cff404a9ebd1624c5f Added check if fontEngine is still in the cache (current HEAD). Changes compared to previous snapshot: http://do

Re: [Development] Upgrading the sources to C++11 keywords (Q_NULLPTR, etc.)

On 2015-01-08 17:33, Thiago Macieira wrote: > I think it's time to institute a policy that we should fix our sources to use > the new C++11 keywords. I'd like to propose the following. > > Policy per keyword: > > * Q_NULLPTR - strongly encouraged > > Use it whenever your literal zero is a null

Re: [Development] Upgrading the sources to C++11 keywords (Q_NULLPTR, etc.)

On Monday 02 February 2015 14:29:21 Matthew Woehlke wrote: > > * Q_DECL_EQ_DEFAULT - really discouraged > > > > > > I can't think of any case where you could use this and let the code still > > compile in C++98, so don't use it > > I'd actually like to see this used where possible and sensible,

Re: [Development] Feature freeze approaching

Some minor ones from me: https://codereview.qt-project.org/105199 https://codereview.qt-project.org/105200 Regards, Konstantin 2015-01-29 14:02 GMT+04:00 Knoll Lars : > Hi everybody, > > Just a short reminder to you all that the feature freeze and branching of > Qt 5.5 is approaching. The curre

[Development] Is QML Item design deliberately hindering C++ interaction?

Is it a design goal of QML/Quick to discourage C++ interaction? I ask because every DevDays talk I attend includes some version of the phrase "any reasonably complex QML application will have C++ doing its back-end work", but yet I keep running into QML classes that hide important Qt C++ classes /

[Development] 5.3 still open?

Hi guys, I fixed a bug for 5.3, but Marc asked if it was still open. I don't know that it isn't? Bo Thorsen, Director, Viking Software. -- Viking Software Qt and C++ developers for hire http://www.vikingsoft.eu ___ Development mailing list Developmen

[Development] 5.5 feature freeze one week later

Hi, As many of you probably have noticed, we had some issues with the CI system over the last week, making it impossible to get integrations through. Because of that we’re delaying the feature freeze for 5.5 by one week to Monday the 16th of February. I hope this will give everybody enough time to

[Development] Deprecating modules with 5.5

Hi, I’d like to mark a few modules as deprecated with 5.5, and most likely remove them from the binary packages with 5.6. These modules are: * Qt WebKit * Qt Declarative (Qt Quick 1) * Qt Script All of these modules are by now a couple of years old, don’t receive updates above the bare minimum a

Re: [Development] 5.3 still open?

It’s not strictly closed, but I don’t think we’ll create a release from 5.3 anymore. Cheers, Lars On 03/02/15 07:52, "Bo Thorsen" wrote: >Hi guys, > >I fixed a bug for 5.3, but Marc asked if it was still open. I don't know >that it isn't? > >Bo Thorsen, >Director, Viking Software. > >-- >Vikin

[Development] Reproducible Qt ; the purpose of QLibraryInfo::buildDate

Hi After a couple of patches [1], most submitted to gerrit, my current qtbase dev build on linux is bitwise reproducible. This is the first step to let end users check that the binaries they recieve actually matches the sources they recieve. The first simple steps is 1) ensure __DATE__, __TIME__

Re: [Development] Deprecating modules with 5.5

> On Feb 3, 2015, at 8:33 AM, Knoll Lars wrote: > > Hi, > > I’d like to mark a few modules as deprecated with 5.5, and most likely > remove them from the binary packages with 5.6. These modules are: > > * Qt WebKit As long as WebEngine is not (yet?) a “full" replacement of Qt WebKit function

Re: [Development] Deprecating modules with 5.5

On 03/02/15 08:47, "Ziller Eike" wrote: > >> On Feb 3, 2015, at 8:33 AM, Knoll Lars >>wrote: >> >> Hi, >> >> I’d like to mark a few modules as deprecated with 5.5, and most likely >> remove them from the binary packages with 5.6. These modules are: >> >> * Qt WebKit > >As long as WebEngine is