Hi,
I'll start turning this thread into a QUIP here (currently empty placeholder
commit):
https://codereview.qt-project.org/#/c/215625/
I'll update the list when I have written something. In the mean time I'd like
to ask for this to become QUIP #99 and hereby reserve the number.
Cheers,
Freder
Am Donnerstag, 7. Dezember 2017, 14:53:06 CET schrieb Frederik Gladhorn:
> Hi all,
>
> I've lately been discussing with a few people in The Qt Company about our
> versioning.
> Historically it was a good idea to not couple Qt Quick too tightly to
> general Qt releases. There were quite some constr
> On 7 Dec 2017, at 16:42, Robin Burchell wrote:
>
> On Thu, Dec 7, 2017, at 02:53 PM, Frederik Gladhorn wrote:
>
>> 2) Make the minor version import optional and we pick the lastest. This
>> should
>> be optional to prevent the name clashes described above and shifts the
>> risk to
>> the us
On 07/12/17 16:06, Jason H wrote:
> Let me ask this, are the versions maintained separately from Qt? If they are,
> then they should bump, but if they aren't you're just wasting effort. It may
> be that modules can be maintained separately, but how often is that done? It
> seems like even Qt 3D
> >1) sync minor versions to Qt release version:
> >For Qt 5.11, we would provide QtQuick.Controls 2.11
> >This way, the challenge for the user is only to find out if it's version 1, 2
> >or 5.
>
> The "match the Qt version" pattern is used by QtPositioning, QtLocation,
> Sensors, QtBluetooth and
On Thu, Dec 7, 2017, at 02:53 PM, Frederik Gladhorn wrote:
> I've lately been discussing with a few people in The Qt Company about our
> versioning.
Thanks for taking the initiative Frederik!
> And a general confusion around which version does what.
> Since we so far don't keep copies of old fun
>1) sync minor versions to Qt release version:
>For Qt 5.11, we would provide QtQuick.Controls 2.11
>This way, the challenge for the user is only to find out if it's version 1, 2
>or 5.
The "match the Qt version" pattern is used by QtPositioning, QtLocation,
Sensors, QtBluetooth and QtNfc too.
> I've lately been discussing with a few people in The Qt Company about our
> versioning.
> Historically it was a good idea to not couple Qt Quick too tightly to general
> Qt releases. There were quite some constraints and added flexibility was nice.
> Qt Quick has matured a lot though, so I thi
On 07.12.2017 15:53, Frederik Gladhorn wrote:
1) sync minor versions to Qt release version:
For Qt 5.11, we would provide QtQuick.Controls 2.11
This way, the challenge for the user is only to find out if it's version 1, 2
or 5.
This sounds troublesome if Qt 6.0 comes when Qt Quick Controls wo
Hi all,
I've lately been discussing with a few people in The Qt Company about our
versioning.
Historically it was a good idea to not couple Qt Quick too tightly to general
Qt releases. There were quite some constraints and added flexibility was nice.
Qt Quick has matured a lot though, so I think
10 matches
Mail list logo
