Re: [Releasing] [Development] HEADS-UP: Branching from '5.8' to '5.8.0' started

As long as we're still merging from 5.6 to 5.8, this is probably a good way to handle things. But since we're now having this on the table, I still believe that we need to consider when to stop doing merges from 5.6 to newer versions. This has been discussed in length at the contributor

Re: [Releasing] [Development] Qt 5.8.0 API review

at Jedrzej's comment in qnetworkproxy.h Laszlo, can you please comment on qeglnativecontext.h Thanks, Lars On 14/11/16 10:37, "Development on behalf of Lars Knoll" <development-bounces+lars.knoll=qt...@qt-project.org on behalf of lars.kn...@qt.io> wrote: Hi, I

Re: [Releasing] [Development] Qt 5.10 pre-built bunaries

On 7 Jun 2017, at 22:09, Thiago Macieira > wrote: On Tuesday, 6 June 2017 23:57:10 PDT Jani Heikkinen wrote: Hi all, There has been discussion ongoing about 5.10 supported platforms and CI configurations. What we haven't agreed yet is

Re: [Releasing] [Development] Qt 5.10 pre-built bunaries

> On 8 Jun 2017, at 08:37, Ville Voutilainen <ville.voutilai...@gmail.com> > wrote: > > On 8 June 2017 at 09:23, Lars Knoll <lars.kn...@qt.io> wrote: >>> I'd like to propose raising the minimum version for GCC to 4.8.1, which is >>> the >>>

Re: [Releasing] [Development] Qt 5.10 pre-built bunaries

Hi Jani, > On 7 Jun 2017, at 08:57, Jani Heikkinen wrote: > > Hi all, > > There has been discussion ongoing about 5.10 supported platforms and CI > configurations. What we haven't agreed yet is Qt 5.10 pre-built binaries. I > don't see big need to change anything from

Re: [Releasing] [Development] Qt 5.10 pre-built bunaries

> On 16 Jun 2017, at 01:27, Sérgio Martins wrote: > > On Tue, Jun 13, 2017 at 11:52 AM, Jani Heikkinen wrote: >> Hi, >> >> As a conclusion of subject: >> >> only change related to pre-built binaries for 5.10 (from Qt 5.9) is dropping >> 32 bit iOS.

Re: [Releasing] [Development] Maintainers, your action needed: Please check if 3rd party components needs to be updated for Qt 5.11 release

> On 12 Apr 2018, at 12:25, Edward Welbourne wrote: > > Jani Heikkinen (12 April 2018 11:18) >> Please check if some 3rd party component needs to be updated for Qt 5.11 >> release. > > There is a new release of CLDR, version 33 (and we've missed version 32, in >

Re: [Releasing] [Interest] Qt 5.9 and OpenSSL 1.1?

> On 22 Mar 2019, at 03:12, Thiago Macieira wrote: > > On Wednesday, 20 March 2019 13:28:41 PDT Thiago Macieira wrote: >> Still, I don't think we should make a release after December this year, >> because of the OpenSSL support. I propose we shorten the 5.9 support to 30 >> months, ending in

Re: [Releasing] [Development] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

> On 4 Feb 2020, at 16:56, Volker Hilsheimer wrote: > >> On 3 Feb 2020, at 06:35, Jani Heikkinen wrote: >> >> Hi all, >> >> Qt 5.15 Feature Freeze is in effect now. So no new features in '5.15' >> anymore. Please update Qt 5.15 new features page >>

Re: [Releasing] [Development] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

I’d be ok with extending the deadline for this one item until end of next week. It shouldn’t be able to break other things as far as I can tell. But would like to hear Jani’s opinion as well. If he’s also ok go ahead, but it really needs to get approved and merged quickly. Cheers, Lars On 4

Re: [Releasing] Meeting minutes from Qt Release Team meeting 01.09.2020

> On 2 Sep 2020, at 12:48, Edward Welbourne wrote: > > Jani Heikkinen (2 September 2020 08:28) wrote: >> Meeting minutes from Qt Release Team meeting Tue 1st September 2020 > [snip] >> - Target is to release Qt 6.0 Alpha ~mid September >> * FF exceptions should be in Alpha but if not those can