Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread André Pönitz
On Tue, Apr 01, 2014 at 03:07:13PM +0200, Christian Kandeler wrote: > On 04/01/2014 02:00 PM, Joerg Bornemann wrote: > > "Darn! I forgot to clone qtjsondb". > > You usually notice that very soon due to the lack of compile errors. Compilation should be dropped anyway. Why spend time on such a pesk

Re: [Development] [Interest] Qt5.2.1+eglfs / WebKit2 running on i.MX6q ?

2014-04-01 Thread Thomas Senyk
On Tuesday, 01 April, 2014 15:48:01 Michael Olbrich wrote: > Hi, > > On Tue, Apr 01, 2014 at 11:27:09AM +0200, Thomas Senyk wrote: > > On Wednesday, 26 February, 2014 12:51:30 BERTIN, NICOLAS wrote: > > > I'm trying to get WebKit2 running on a Linux/i.MX6Q board (sabresd). I > > > succeeded in bui

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Tony Van Eerd
> > So, here is what we will do: > - create one branch named 'qt' out of current stable > - block any other branches in gerrit > - move on with this branch, and announce the current status of it (open for > features, feature freeze, hardening...) on the mailing list > > In addition there seems to

Re: [Development] [Interest] Qt5.2.1+eglfs / WebKit2 running on i.MX6q ?

2014-04-01 Thread Michael Olbrich
Hi, On Tue, Apr 01, 2014 at 11:27:09AM +0200, Thomas Senyk wrote: > On Wednesday, 26 February, 2014 12:51:30 BERTIN, NICOLAS wrote: > > I'm trying to get WebKit2 running on a Linux/i.MX6Q board (sabresd). I > > succeeded in building Qt5.2.1+eglfs and the WebKit1 based examples are > > running well

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Rutledge Shawn
On 1 Apr 2014, at 2:37 PM, André Somers wrote: > Diego Iastrubni schreef op 1-4-2014 14:17: >> I agree. >> >> As we move to a more linear development cycle, we can finally drop >> git and update to svn, "where we are going we don't need branches" >> anyway. > I'd actually like to suggest an upg

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Christian Kandeler
On 04/01/2014 02:00 PM, Joerg Bornemann wrote: > "Darn! I forgot to clone qtjsondb". You usually notice that very soon due to the lack of compile errors. Christian ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mai

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Stephen Kelly
On Tuesday, April 01, 2014 11:12:18 Koehne Kai wrote: > I had a discussion with this with a couple of people, including Lars. In the > end we realized that both models are too complicated, and we should rather > have only one branch. Reality shows that we're working pretty sequential, > anyway: Eve

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Bruning Michael
>> I agree. >> >> As we move to a more linear development cycle, we can finally drop >> git and update to svn, "where we are going we don't need branches" >> anyway. > I'd actually like to suggest an upgrade to CSV then. I'd say get rid off complicated systems etc altogether and use an ftp server

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread André Somers
Diego Iastrubni schreef op 1-4-2014 14:17: > I agree. > > As we move to a more linear development cycle, we can finally drop > git and update to svn, "where we are going we don't need branches" > anyway. I'd actually like to suggest an upgrade to CSV then. André _

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Diego Iastrubni
I agree. As we move to a more linear development cycle, we can finally drop git and update to svn, "where we are going we don't need branches" anyway. On Tue, Apr 1, 2014 at 2:12 PM, Koehne Kai wrote: > Hi, > > We've had now different setups with git branches - in Qt 4 we followed a > scheme w

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Paul Olav Tvete
On Tuesday 01 April 2014 11:12:18 Koehne Kai wrote: > So, here is what we will do: > - create one branch named 'qt' out of current stable > - block any other branches in gerrit > - move on with this branch, and announce the current status of it (open for > features, feature freeze, hardening...) on

Re: [Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Joerg Bornemann
On 01-Apr-14 13:12, Koehne Kai wrote: > If there are no fundamental objections I'd like to see this into action as > early as possible, to not risk the 5.3.0 release (i.e. next week Thursday, > when we originally planned to merge to release branch). I'm all for it. We also should integrate all

Re: [Development] Nominating Giulio Camuffo (giucam) as an Approver

2014-04-01 Thread Gunnar Sletta
+1 On 01 Apr 2014, at 12:58, Nichols Andy wrote: > Hello fellow Qt developers, > > I would like to nominate Giulio Camuffo for Qt Project approver status. > Giulio has been contributing to the QtWayland module for over a year now with > both quality code submissions as well as code reviews. >

Re: [Development] Nominating Giulio Camuffo (giucam) as an Approver

2014-04-01 Thread Agocs Laszlo
+1 From: development-bounces+laszlo.agocs=digia@qt-project.org [development-bounces+laszlo.agocs=digia@qt-project.org] on behalf of Jorgen Lind [jorgen.l...@digia.com] Sent: Tuesday, April 01, 2014 1:17 PM To: development@qt-project.org Subject: Re

Re: [Development] Nominating Giulio Camuffo (giucam) as an Approver

2014-04-01 Thread Jorgen Lind
+1 On Tuesday 01 April 2014 10:58:11 Nichols Andy wrote: > Hello fellow Qt developers, > > I would like to nominate Giulio Camuffo for Qt Project approver status. > Giulio has been contributing to the QtWayland module for over a year now > with both quality code submissions as well as code review

[Development] One 'qt' branch to rule 'em all!

2014-04-01 Thread Koehne Kai
Hi, We've had now different setups with git branches - in Qt 4 we followed a scheme with one master branch, which gets forked into minor version branches (e.g. 4.8), which gets forked into patch branches (e.g. 4.8.1) ... in Qt 5 we adopted a model where we had only three branches: dev, stable,

Re: [Development] Nominating Giulio Camuffo (giucam) as an Approver

2014-04-01 Thread Knight Andrew
+1 Seconded. Having followed giucam's contributions to QtWayland and discussions on IRC, I have to agree that he would make a valuable Approver for QtWayland and the Qt Project in general. > -Original Message- > From: development-bounces+andrew.knight=digia@qt-project.org > [mailto:

[Development] Nominating Giulio Camuffo (giucam) as an Approver

2014-04-01 Thread Nichols Andy
Hello fellow Qt developers, I would like to nominate Giulio Camuffo for Qt Project approver status. Giulio has been contributing to the QtWayland module for over a year now with both quality code submissions as well as code reviews. He is easy to get in touch with on IRC, and is responsive when a

Re: [Development] [Interest] Qt5.2.1+eglfs / WebKit2 running on i.MX6q ?

2014-04-01 Thread Thomas Senyk
On Wednesday, 26 February, 2014 12:51:30 BERTIN, NICOLAS wrote: > Hey all, > > I'm trying to get WebKit2 running on a Linux/i.MX6Q board (sabresd). I > succeeded in building Qt5.2.1+eglfs and the WebKit1 based examples are > running well. > > Now, I'm trying to get WebKit2 running: the MiniBrowse

[Development] CI Jenkins restart

2014-04-01 Thread Sarajärvi Tony
Hi We got tired of restarting Jenkins twice a week, so I tweaked the machine a bit. It now has 6 cores instead of 2, it has 24 gigs of memory instead of 8, I adjusted Jenkins to use max heap size of 8gb instead of 1gb and maxpermsize was increased to 4096 from 512. Sorry for breaking your curr