Hi!
We have branched '6.6.2' from '6.6'. So from now on all changes targeted to Qt
6.6.2 release must have 'Pick-to: 6.6.2' and '6.6' is for Qt 6.6.3 release. As
usual staging in '6.6.2' is restricted to release team only and we will monitor
incoming changes and stage the clear ones in
Il 22/01/24 19:03, Shawn Rutledge via Development ha scritto:
I guess your goal is to be able to see it in the header rather than
having to look up the docs in the cpp file or online? (Alternatively we
could write all docs in headers, but then the headers get to be large,
take storage space
This was (sadly) a bug, see comments:
https://bugreports.qt.io/browse/QTBUG-117783
Cheers ,
Eli
On 1/22/2024 10:29 AM, Frank Meerkötter wrote:
I am looking for a clarification on the licensing of the Protobuf-Module.
The code in https://code.qt.io/cgit/qt/qtgrpc.git/tree/src/protobuf
has
On Jan 22, 2024, at 10:41 AM, Giuseppe D'Angelo via Development
wrote:
Hi,
A number of classes and functions that are going to be introduced in 6.7 are
meant to be "tech preview", and thus they may pass the header review even if we
are aware of some limitations or issues with their design.
Hi,
A number of classes and functions that are going to be introduced in 6.7
are meant to be "tech preview", and thus they may pass the header review
even if we are aware of some limitations or issues with their design.
I propose to introduce a macro, QT_TECH_PREVIEW_API (bikeshed please),
I am looking for a clarification on the licensing of the Protobuf-Module.
The code in https://code.qt.io/cgit/qt/qtgrpc.git/tree/src/protobuf has
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR LGPL-3.0-only OR
GPL-2.0-only OR GPL-3.0-only
While the code in
