On Wednesday, 6 February 2019 04:40:24 PST Tuukka Turunen wrote:
> I do agree that we should avoid dropping configurations in patch releases.
> However, we should be pragmatic and provide the set that is most valuable
> for the users and still feasible to maintain. So in my opinion adding
>
On Wed, 6 Feb 2019 at 12:43, Giuseppe D'Angelo via Development
wrote:
>
> Il 05/02/19 18:16, Dmitriy Purgin ha scritto:
> > I couldn't figure out the exact combination but as far as I remember, if
> > you have namespaced code, you have to always fully qualify the enum
> > class parameters in
Hi,
I do agree that we should avoid dropping configurations in patch releases.
However, we should be pragmatic and provide the set that is most valuable for
the users and still feasible to maintain. So in my opinion adding something and
removing another is fine if that is what best serves our
> -Original Message-
> From: Development On Behalf Of
> The mail did not state 5.12.x. Hence it was under the assumption "as always"
> with the next minor release.
As the person who initiated this, I have a bit of an ambivalent view point.
Fact is, we have always made those changes for
Am Mi., 6. Feb. 2019 um 13:01 Uhr schrieb Jesus Fernandez <
jesus.fernan...@qt.io>:
>
> The original mail said nothing about 5.12.2. And I would remove support
> for both compilers in 5.13. Any 32 bits is an outdated platform.
>
>
>
32 bit is not only about platform. 32 bit applications still run
The mail did not state 5.12.x. Hence it was under the assumption "as always"
with the next minor release.
Maurice
> -Original Message-
> From: Jani Heikkinen
> Sent: Wednesday, February 6, 2019 12:54 PM
> To: Jesus Fernandez ; Maurice Kalinowski
> ; Simon Hausmann
> Cc:
Hi!
The original mail said nothing about 5.12.2. And I would remove support for
both compilers in 5.13. Any 32 bits is an outdated platform.
Best regards,
Jesús
From: Jani Heikkinen
Sent: 06 February 2019 12:54
To: Jesus Fernandez; Maurice Kalinowski; Simon
Hi!
>>And I think we started providing binaries for a platform in 5.12.0 we cannot
>>stop providing them in 5.12.x.
I disagree. I agree we shouldn't do this kind of decisions without good reasons
but I don't see anything why we couldn't do this kind of changes if there is
good reasons. This is
Dear Qt developers,
We have removed Qt Telemetry repository from the Qt Project playground due to a
possible copyright violation.
Based on analysis of the code, we have a reason to believe some of the
contributed code is in violation of the Qt Project CLA.
According to the Qt Project CLA all
> I think what Jesus refers to is patch level releases.
Yes, I was referring to patch releases.
And I think we started providing binaries for a platform in 5.12.0 we cannot
stop providing them in 5.12.x.
Best regards,
Jesús
From: Jani Heikkinen
Sent: 06
Hi,
As Simon already wrote this is affecting only prebuilt binary packages we
deliver and nothing else. It is true that we usually haven't touched (at least
removed) those in patch level releases but I don't see any big issue with doing
this now; UWP x86 msvc 2015 isn't that widely used and
I think what Jesus refers to is patch level releases.
We’ve been changing binary packages for platforms within minor releases so far,
but not for patch level ones.
Maurice
From: Development On Behalf Of Simon
Hausmann
Sent: Wednesday, February 6, 2019 9:19 AM
To: Jesus Fernandez
Cc:
That’s why it is always good practice to only use FQTN in public headers anyway
;)
Beste Grüße / Best regards,
Alexander Nassian
> Am 06.02.2019 um 05:41 schrieb Giuseppe D'Angelo via Development
> :
>
> Il 05/02/19 18:16, Dmitriy Purgin ha scritto:
>> I couldn't figure out the exact
Afaik this merely affects the binaries provided in the installer. It does not
result in any changes in the git repos.
Simon
On 5. Feb 2019, at 16:03, Jesus Fernandez
mailto:jesus.fernan...@qt.io>> wrote:
Can we remove a platform in a minor version?
Best regards,
Jesús
Original
14 matches
Mail list logo