On Monday 22 June 2015 10:35:56 rpzrpz...@gmail.com wrote:
> On 6/22/2015 9:16 AM, Thiago Macieira wrote:
> > On Monday 22 June 2015 06:56:25 rpzrpz...@gmail.com wrote:
> >> Don't have the manpower?
> >>
> >> Then transfer LTS support over to a group of willing volunteers whose
> >> businesses dep
On 6/22/2015 9:16 AM, Thiago Macieira wrote:
> On Monday 22 June 2015 06:56:25 rpzrpz...@gmail.com wrote:
>> Don't have the manpower?
>>
>> Then transfer LTS support over to a group of willing volunteers whose
>> businesses depend on it and let them handle as a GROUP the maintenance.
>
> Is anyone
On Monday 22 June 2015 06:56:25 rpzrpz...@gmail.com wrote:
> Don't have the manpower?
>
> Then transfer LTS support over to a group of willing volunteers whose
> businesses depend on it and let them handle as a GROUP the maintenance.
Is anyone volunteering?
--
Thiago Macieira - thiago.macieira
uot;Gunnar Roth" , "Knoll Lars"
Cc: "development@qt-project.org" , "Thiago Macieira"
Betreff: RE: [Development] QtCS: Long Term Release discussion
So this bit in the article is not factual?
"Windows Embedded Compact no longer provides its own tool chain (compile
theqtcompany.com@qt-
> project.org [mailto:development-bounces+louai.al-
> khanji=theqtcompany@qt-project.org] On Behalf Of Gunnar Roth
> Sent: Friday, June 19, 2015 7:50 PM
> To: Knoll Lars
> Cc: development@qt-project.org; Thiago Macieira
> Subject: Re: [Development]
Don't have the manpower?
Then transfer LTS support over to a group of willing volunteers whose
businesses depend on it and let them handle as a GROUP the maintenance.
Provide a space on the the Qt Web Site for organizing reasons and make
it officially a "community" only supported pile of code.
> Am 19.06.2015 um 18:38 schrieb Knoll Lars :
>
>
> There was never an intention to remove it after 5.6. But I was hoping that we
> could be using VC++ 2013 (and support wec2013 with it). Looks like that is
> unfortunately not the case. That implies that our new compiler baseline will
> stay
On 19/06/15 18:26,
"development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of
Gunnar Roth" wrote:
>
>Hi Björn,
>i am really glad this discussion will come to an end ;-), it already took
>considerable time, internally and externally.
>> Am 19.06.2015 um 17:51 schrieb Björn B
Hi Björn,
i am really glad this discussion will come to an end ;-), it already took
considerable time, internally and externally.
> Am 19.06.2015 um 17:51 schrieb Björn Breitmeyer :
>
> Hi Gunnar,
>
> sadly i have to agree. I finally had the time to setup a Visual Studio 2013
> with the recent
um 11:48 Uhr
> Von: "Björn Breitmeyer"
> An: "Gunnar Roth"
> Cc: development@qt-project.org, "Thiago Macieira"
> Betreff: Re: Aw: Re: [Development] QtCS: Long
> Term Release discussion That would be this one,
>
> https://msdn.microsoft.com/en-us/l
rg, "Thiago Macieira"
Betreff: Re: Aw: Re: [Development] QtCS: Long Term Release discussion
That would be this one,
https://msdn.microsoft.com/en-us/library/gg154234.aspx
btw, i would assume the use of the newer libstdc++ if i got it right, as that
one comes from the sdk too. But may
>
> Gesendet: Donnerstag, 18. Juni 2015 um 10:41 Uhr
> Von: "Björn Breitmeyer"
> An: development@qt-project.org
> Cc: "Gunnar Roth" , "Thiago Macieira"
> Betreff: Re: [Development] QtCS: Long Term
> Release discussion
> Hello Gunnar,
>
on: "Björn Breitmeyer"
An: development@qt-project.org
Cc: "Gunnar Roth" , "Thiago Macieira"
Betreff: Re: [Development] QtCS: Long Term Release discussion
Hello Gunnar,
i still hadn't time to verify this, but. There is a platform builder for
WEC2013, if you gene
Juni 2015, 10:16:49 schrieb Gunnar Roth:
> Gesendet: Donnerstag, 18. Juni 2015 um 08:43 Uhr
> Von: "Thiago Macieira"
> An: development@qt-project.org
> Betreff: Re: [Development] QtCS: Long Term Release discussion
>
> On Thursday 18 June 2015 08:23:52 Gunnar Roth wro
solutions
Am Donnerstag, 18. Juni 2015, 10:16:49 schrieb Gunnar Roth:
> Gesendet: Donnerstag, 18. Juni 2015 um 08:43 Uhr
> Von: "Thiago Macieira"
> An: development@qt-project.org
> Betreff: Re: [Development] QtCS: Long Term Release discussion
>
> On Thursday 18 June
Gesendet: Donnerstag, 18. Juni 2015 um 08:43 Uhr
Von: "Thiago Macieira"
An: development@qt-project.org
Betreff: Re: [Development] QtCS: Long Term Release discussion
On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote:
> > Am 17.06.2015 um 22:35 schrieb Thiago Macieira
&
ect.org"
Betreff: Re: [Development] QtCS: Long Term Release discussion
> On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote:
> > > Am 17.06.2015 um 22:35 schrieb Thiago Macieira
> > > :
> > >
> > > On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote:
&g
> On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote:
> > > Am 17.06.2015 um 22:35 schrieb Thiago Macieira
> > > :
> > >
> > > On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote:
> > >> Yes that would make us (as a commercial user using a self made
> > >> port of qt
> > >> 5.4.1 to wec2013 ) ve
On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote:
> > Am 17.06.2015 um 22:35 schrieb Thiago Macieira
> > :
> >
> > On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote:
> >> Yes that would make us (as a commercial user using a self made port of
> >> qt
> >> 5.4.1 to wec2013 ) very unhappy. Thi
> Am 17.06.2015 um 22:35 schrieb Thiago Macieira :
>
> On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote:
>> Yes that would make us (as a commercial user using a self made port of qt
>> 5.4.1 to wec2013 ) very unhappy. This means 5.6 will be the last version
>> wec2013 would be supported and
On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote:
> Yes that would make us (as a commercial user using a self made port of qt
> 5.4.1 to wec2013 ) very unhappy. This means 5.6 will be the last version
> wec2013 would be supported and you would go straight to making a back port
> very hard or e
Hello Lars,
> Am 17.06.2015 um 12:27 schrieb Knoll Lars :
>
> * We make Qt 5.6 an LTS release
> * We could then have both WEC7 and WEC2013 (on VS2012) supported on 5.6.
> This would solve all problems for Windows Embedded and we could make
> VS2013 the compiler baseline for 5.7.
> we’d keep peopl
On Wednesday 17 June 2015 18:50:14 André Pönitz wrote:
> Would be possible to freeze 5.6 right now, and release that quickly
> after 5.5 as LTS, already running on the new CI, and do whatever
> else was originally planned for 5.6 in 5.7?
I don't think we can do two releases in the next 7 months. W
On Wed, Jun 17, 2015 at 07:31:19AM -0700, Thiago Macieira wrote:
> On Wednesday 17 June 2015 10:34:39 Giuseppe D'Angelo wrote:
> > > Since 5.5 LTS is an impossibility, the only alternative to minimising the
> > > issues is to push the deprecations to 5.7 and do one more "official"
> > > release of
On Wednesday 17 June 2015 10:34:39 Giuseppe D'Angelo wrote:
> > Since 5.5 LTS is an impossibility, the only alternative to minimising the
> > issues is to push the deprecations to 5.7 and do one more "official"
> > release of the to-be-deprecated code in 5.6.
>
> I would agree to this plan; we can
On Wed, Jun 17, 2015 at 10:44:38AM +, Knoll Lars wrote:
> On 17/06/15 12:34, "André Somers" wrote:
>
> >Knoll Lars schreef op 17-6-2015 om 12:27:
> >> * We’d still remove the deprecated modules from our Qt 5.6 release
> >>(maybe
> >> with the exception of Qt Script).
> >Is that really needed?
On 17/06/15 12:34, "André Somers" wrote:
>Knoll Lars schreef op 17-6-2015 om 12:27:
>> * We’d still remove the deprecated modules from our Qt 5.6 release
>>(maybe
>> with the exception of Qt Script).
>Is that really needed? For all of the modules? Could Quick 1 stay too?*
>
>André
> *) Yes, we h
Knoll Lars schreef op 17-6-2015 om 12:27:
> * We’d still remove the deprecated modules from our Qt 5.6 release (maybe
> with the exception of Qt Script).
Is that really needed? For all of the modules? Could Quick 1 stay too?*
André
*) Yes, we have a stake in that: The printing case.
___
Going through the discussions and looking at our time schedule, here’s
another proposal how we could do things (slightly different from what we
discussed at QtCS):
* We make Qt 5.6 an LTS release
* We already have of the current dev branch on pretty much all platforms
supported in Qt 5.5 working i
Giuseppe D'Angelo schreef op 17-6-2015 om 10:34:
> I would also push the "C++11 in our API" to 5.7 to minimise the risks.
> Cheers,
C++11 in our API was to be taken slowly anyway, according to the session
at QtCS. We would start with using it in the implementation to gain some
experience first.
On 17/06/15 10:34, "Giuseppe D'Angelo" wrote:
>On Wed, Jun 17, 2015 at 9:15 AM, Thiago Macieira
> wrote:
>>
>> Two different CI implementations. The "new CI" is being developed in
>>lockstep
>> with Qt 5.6, including QtTest features. That means the "new CI" system
>>cannot
>> be backported to 5.5
On Wed, Jun 17, 2015 at 9:15 AM, Thiago Macieira
wrote:
>
> Two different CI implementations. The "new CI" is being developed in lockstep
> with Qt 5.6, including QtTest features. That means the "new CI" system cannot
> be backported to 5.5.
Ok, thanks for explaining this out...
> In turn, to ke
Thiago Macieira schreef op 17-6-2015 om 09:15:
> On Wednesday 17 June 2015 09:01:19 André Somers wrote:
>> Does the CI infrastructure depend on the Qt version then? What is it
>> about 5.5 that prevents the CI from being upgraded?
> Two different CI implementations. The "new CI" is being develope
On Wednesday 17 June 2015 09:01:19 André Somers wrote:
> Thiago Macieira schreef op 17-6-2015 om 08:57:
> > On Wednesday 17 June 2015 08:33:50 Giuseppe D'Angelo wrote:
> >> On Tue, Jun 16, 2015 at 10:49 PM, Thiago Macieira
> >>
> >> wrote:
> >>> Qt 5.5 would be ideal - but we'd need to support th
On Tuesday, June 16, 2015 01:49:54 PM Thiago Macieira wrote:
[...]
> Other notes:
> * We will keep a Linux builder building 32-bit to make sure everything
> works - *no binary packages for Linux 32-bit*
We do have at least one Linux builder today that targets armv7, but AFAICS
that is the o
On Wednesday 17 June 2015 08:35:58 André Somers wrote:
> Thiago Macieira schreef op 16-6-2015 om 22:49:
> > Last year's notes[1]
> >
> > Qt 5.5 will be the last release to support:
> > * GCC 4.6
> > * OS X 10.7
> > * Windows Vista
> > * WIndows Embedded Compact 7
> >
Thiago Macieira schreef op 17-6-2015 om 08:57:
> On Wednesday 17 June 2015 08:33:50 Giuseppe D'Angelo wrote:
>> On Tue, Jun 16, 2015 at 10:49 PM, Thiago Macieira
>>
>> wrote:
>>> Qt 5.5 would be ideal - but we'd need to support the old Qt CI system for
>>> longer. So we're targetting that *Qt 5.6*
On Wednesday 17 June 2015 08:33:50 Giuseppe D'Angelo wrote:
> On Tue, Jun 16, 2015 at 10:49 PM, Thiago Macieira
>
> wrote:
> > Qt 5.5 would be ideal - but we'd need to support the old Qt CI system for
> > longer. So we're targetting that *Qt 5.6* will be the first LTS release.
>
> Mind to elabor
Thiago Macieira schreef op 16-6-2015 om 22:49:
> Last year's notes[1]
>
> Qt 5.5 will be the last release to support:
> * GCC 4.6
> * OS X 10.7
> * Windows Vista
> * WIndows Embedded Compact 7
> * QNX 6.5
> * Qt WebKit, Qt Script, Qt Quick 1
Ok, I understan
On Tue, Jun 16, 2015 at 10:49 PM, Thiago Macieira
wrote:
>
> Qt 5.5 would be ideal - but we'd need to support the old Qt CI system for
> longer. So we're targetting that *Qt 5.6* will be the first LTS release.
Mind to elaborate? Why is the "old Qt CI" a requirement or a blocker
for a LTS release?
Last year's notes[1]
Qt 5.5 will be the last release to support:
* GCC 4.6
* OS X 10.7
* Windows Vista
* WIndows Embedded Compact 7
* QNX 6.5
* Qt WebKit, Qt Script, Qt Quick 1
Therefore, we'd like to have a long-term support release that allows people
who can
41 matches
Mail list logo
