[Development] Qt 5.6.2 Snapshot for testing

2016-09-08 Thread Jani Heikkinen
Hi all, We have Qt 5.6.2 snapshot for testing Win: http://download.qt.io/snapshots/qt/5.6/5.6.2/553/ Linux: http://download.qt.io/snapshots/qt/5.6/5.6.2/489/ Mac:

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-09-08 Thread Alexander Blasche
From: Marc Mutz >On Wednesday 07 September 2016 08:37:01 Friedemann Kleint wrote: >> ** After 5.7 is closed and sanity bot is upgraded (to handle >> cherry-picking), go into cherrypicking mode for 5.6. Developer is >> responsible for

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-09-08 Thread Liang Qi
On 8 September 2016 at 09:36, Alexander Blasche wrote: > > From: Marc Mutz > > >On Wednesday 07 September 2016 08:37:01 Friedemann Kleint wrote: > >> ** After 5.7 is closed and sanity bot is upgraded (to

[Development] QUuid documentation

2016-09-08 Thread Benjamin TERRIER
Hi, As of Qt 5.7, QUuid::createUuid() documentation is: > On any platform other than Windows, this function returns a new UUID with > variant QUuid::DCE and version QUuid::Random. If the /dev/urandom device > exists, then the numbers used to construct the UUID will be of cryptographic >

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-09-08 Thread Liang Qi
On 7 September 2016 at 08:37, Friedemann Kleint wrote: > Hi, > > the notes are at: https://wiki.qt.io/QtCS2016_Managing_Qt_Branches > > * Number of existing branches (5.6LTS, 5.7.,5.8 dev) causes a number of > problems > > ** Strain on COIN which also has release

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-09-08 Thread Marc Mutz
On Wednesday 07 September 2016 08:37:01 Friedemann Kleint wrote: > ** After 5.7 is closed and sanity bot is upgraded (to handle > cherry-picking), go into cherrypicking mode for 5.6. Developer is > responsible for doing the cherrypicking > ** Cherry-picking technicalities need to be figured out:

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Milian Wolff
On Donnerstag, 8. September 2016 13:41:21 CEST Bo Thorsen wrote: > Den 05-09-2016 kl. 20:49 skrev Milian Wolff: > >> As an incredibly simple example, make is inherently limited in that it > >> > >> > cannot even represent a rule with multiple outputs (there are some > >> > workarounds, but they

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Christian Kandeler
On 09/08/2016 02:03 PM, Bo Thorsen wrote: > Ok, go try it. Create a simple python or perl script that reads a file. > The file just has a single number N inside it. And based on N the script > outputs those files: > > server.h > method1.h > method2.h > ... > methodN.h > > Inside method1.h you

Re: [Development] [Qt-creator] [FYI] on gerrit change retargeting requests

2016-09-08 Thread Oswald Buddenhagen
On Tue, Sep 06, 2016 at 02:56:31PM +0200, Marc Mutz wrote: > As it is now, not even all @qt.io people know how to do this/that it's > possible... > of course. why would anyone read the branch creation mails in which we point out the possibility every single time ... it's not like they have

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Bo Thorsen
Den 08-09-2016 kl. 13:47 skrev Milian Wolff: On Donnerstag, 8. September 2016 13:41:21 CEST Bo Thorsen wrote: Den 05-09-2016 kl. 20:49 skrev Milian Wolff: As an incredibly simple example, make is inherently limited in that it cannot even represent a rule with multiple outputs (there are some

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Konstantin Tokarev
08.09.2016, 15:03, "Bo Thorsen" : > Den 08-09-2016 kl. 13:47 skrev Milian Wolff: >>  On Donnerstag, 8. September 2016 13:41:21 CEST Bo Thorsen wrote: >>>  Den 05-09-2016 kl. 20:49 skrev Milian Wolff: >  As an incredibly simple example, make is inherently limited in that

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Milian Wolff
On Donnerstag, 8. September 2016 14:03:05 CEST Bo Thorsen wrote: > Den 08-09-2016 kl. 13:47 skrev Milian Wolff: > > On Donnerstag, 8. September 2016 13:41:21 CEST Bo Thorsen wrote: > >> Den 05-09-2016 kl. 20:49 skrev Milian Wolff: > As an incredibly simple example, make is inherently limited

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-09-08 Thread Oswald Buddenhagen
On Thu, Sep 08, 2016 at 12:25:02PM +0200, Liang Qi wrote: > This is mainly because we did heavy refactoring in upstream branches, > "upstream" makes no sense whatsoever. merge-wise, it's exactly the wrong way around. "younger" as used elsewhere in this thread is better. > for example, rewriting

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Bo Thorsen
Den 05-09-2016 kl. 20:49 skrev Milian Wolff: As an incredibly simple example, make is inherently limited in that it > cannot even represent a rule with multiple outputs (there are some > workarounds, but they are hacky and rather limited in how they can be > applied). And ninja is no magic

Re: [Development] Qt Network Maintainership Changes

2016-09-08 Thread Edward Welbourne
On 6 Sep 2016, at 21:05, Richard Moore wrote: >> [...] I'd like to nominate Timur as my replacement - he's already >> spent an inordinate amount of time fixing bugs, to say nothing of >> adding support for HTTP/2 so I'm sure things are in good hands. >> >>

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Bo Thorsen
Den 08-09-2016 kl. 14:19 skrev Konstantin Tokarev: > The only problem is that you have to run moc on each of the .h files. Run moc from inside script when you generate header. Yes, I thought about that at the time as well. While simple enpough, there are some complications. You would have to

Re: [Development] Which changes are suitable for 5.6?

2016-09-08 Thread Edward Welbourne
On Wednesday 07 September 2016 10:26:44 Olivier Goffart wrote: >> The reason we should limit the changes to critical change is so than >> "jumping through hoops" gets easier. Every patch we put there instead >> of in a upper branch makes more work of merging, handling regressions >> causing by

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

2016-09-08 Thread Thiago Macieira
On quinta-feira, 8 de setembro de 2016 07:37:28 PDT Liang Qi wrote: > Is it better to have 5.7.2 around 5.8.0 final release and close 5.7 after > that? 5.7.1 is very soon in a few weeks. There will be a few months gap > between 5.7.1 and 5.8.0/5.8.1. The first release of new branch, like 5.8.0, >

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Stephen Kelly via Development
On 08/09/16 14:48, Milian Wolff wrote: Someone else also told me that this is apparently harder then I thought it is with CMake, when the name of the output files of a code generator is not known. It is possible, but far from easy esp. when you don't have control over the generator script

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

2016-09-08 Thread Jake Petroules
Another thing that's very hard to do in other build systems is building Java code. The class files emitted by a Java compiler actually vary depending on the contents of the Java files themselves. Imagine you've built a JAR file, and then you add a new anonymous inner class within one of your