[Development] HEADS-UP: Branching from '6.4' to '6.4.2' done

Good morning! We have branched '6.4.2' from '6.4' now and so on all changes targeted to Qt 6.4.2 release must have 'Pick-to: 6.4.2' and '6.4' is for Qt 6.4.3 release. As usual staging in '6.4.2' will be restricted to release team only and we will monitor and stage needed changes automatically

[Development] Multi-subarch update

Hello all A few of us have just had a call to discuss what we're going to do for the functionality I proposed for 6.5. Here are our conclusions and proposals. First, we're going to postpone this to 6.6, on account of feature freeze being too close. While I think the risk is minimal for

Re: [Development] How qAsConst and qExchange lead to qNN

On Wed, Nov 16, 2022 at 09:50:35AM -0800, Thiago Macieira wrote: > On Tuesday, 15 November 2022 23:50:38 PST Marc Mutz via Development wrote: > > > in a thread-safe manner (such that if something in > > > the same thread or another thread-safely modifies that map, the original > > > user isn't

Re: [Development] How qAsConst and qExchange lead to qNN

On Tue, Nov 15, 2022 at 08:07:50AM +, Marc Mutz via Development wrote: > On 14.11.22 23:04, A. Pönitz wrote: > >> Marc’s proposal of a Non-Owning Interface is already > >> become manifest in QRegion::begin/end > >> > >> https://doc.qt.io/qt-6/qregion.html#begin > >> > >> allowing us to write >