Re: [Development] Spam: Re: Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Thiago Macieira]

On Monday, 4 January 2021 20:32:27 -03 Scott Bloom wrote:
> The funny thing, I remember at a Qt Dev Days when Qt 5 was about a year
> away.  The "we will never do a Qt 3-4 type major version change again" was
> said time and time again.
> 
> Where functionality was missing, and no one was happy with Qt 4.0 except the
> people who got to say "4.0" released

Both statements are true but their combination is misleading.

Yes, Qt developers promised never to do a Qt 3 to 4 transition again. Yes, Qt 
4.0 was missing some functionality from Qt 3, which made 4.0 an impossible 
target, as well as having brand new functionality that was hadn't yet matured 
(itemviews).

But the first statement is taken out of context and thus makes it sound that 
the second statement is the reason for the first. It is not. The reason why we 
didn't want a 4.0 transition is because of the massive amount of code changes 
that were required for code bases to transition to 4.0. That is not the case 
here, as most codebases can compile with 6.x with limited porting effort.

It's also true that some of them can't be ported to 6.0, but once 6.1 and 6.2 
come along, they will be.

The concern raised by people who can't move forward and aren't getting bug 
fixes either is a valid one, though.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Spam: Re: Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Scott Bloom]

-Original Message-
From: Development  On Behalf Of Kevin 
Kofler via Development
Sent: Monday, January 4, 2021 3:16 PM
To: development@qt-project.org
Subject: Re: [Development] Spam: Re: Commercial-only LTS phase starts: Closing 
the 5.15 branch(es) on 5th January

Oswald Buddenhagen wrote:
> one can always say that, but there is a balance to be struck, and it 
> is
> *very* obvious that 6.1 will be what and when 6.0 should have been.
> whether BC is broken doesn't even matter at that point, because no-one 
> sane who depends on binary compat will touch 6.0 with a ten-foot pole 
> now. also, i've been watching qtcore dev closely, and _no-one_ behaved 
> as if a release was imminent, for good reason - it simply wasn't ready 
> yet, everything still being in flux.

Basically, Qt is making the same mistake with 6.0 that KDE made with 4.0: 
releasing a .0 that even the developers do not recommend actually depending on, 
just for the sake of releasing something.

Kevin Kofler


The funny thing, I remember at a Qt Dev Days when Qt 5 was about a year away.  
The "we will never do a Qt 3-4 type major version change again" was said time 
and time again.

Where functionality was missing, and no one was happy with Qt 4.0 except the 
people who got to say "4.0" released

Scott
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[David Edmundson]

I need some version clarification.

Is Qt 5.15.3 in the "strict" phase of the Qt LTS?

I have approved changes into Qt 5.15.3 under the assumption that we
are still in the stable phase, as I have not seen any emails to the
contrary.

I assumed this as the QUIP [1]  states:
>strict: This period starts when the one after next stable branch is created 
>(for the 5.12 LTS, the one after next was 5.14). Upgrading the Qt libraries 
>(within LTS) must not put installed applications at risk of breaking. Breaking 
>existing bug workarounds is therefore not allowed, even if the bug is fixed.

Which we are not yet in for Qt 5.15.


The same QUIP also states:

>Note: From 5.15 onwards, the extension of the stable phase becomes a service 
>for users of Qt under the commercial license.

If Qt 5.15.3 is for commercial users only, we must have entered the
strict phase.
Can you clarify which LTS state Qt 5.15.3 will be in. I might need to
double check my approvals.

David Edmundson

[1] http://quips-qt-io.herokuapp.com/quip-0016-branch-policy.html
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Spam: Re: Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Oswald Buddenhagen]

On Mon, Jan 04, 2021 at 07:55:10PM +, Volker Hilsheimer wrote:
It seems that releasing a 6.0 was the best way to get more eyes and 
brains on Qt 6.


one can always say that, but there is a balance to be struck, and it is 
*very* obvious that 6.1 will be what and when 6.0 should have been.  
whether BC is broken doesn't even matter at that point, because no-one 
sane who depends on binary compat will touch 6.0 with a ten-foot pole 
now. also, i've been watching qtcore dev closely, and _no-one_ behaved 
as if a release was imminent, for good reason - it simply wasn't ready 
yet, everything still being in flux.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Spam: Re: Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Volker Hilsheimer]

> On 4 Jan 2021, at 16:53, Bernhard Lindner  wrote:
> 
> 
>> I’m not aware of a decision to break binary compatibility in Qt 6.1. The - 
>> so far - last
>> email to the respective discussion thread is
>> 
>> https://lists.qt-project.org/pipermail/development/2020-December/040763.html
>> 
>> and neither that nor any of the previous emails are conclusively stating 
>> that we do or
>> don’t break BC.
> 
> If you are right, I got it wrong as well.
> 
>> The topic in this particular thread is controversial enough as it is, let’s 
>> stick to the
>> facts :)
> 
> This is a good idea all the time.
> 
> Still Oswald was right. Qt 6 is a cripple (independent of the binary 
> compatibility
> questions) and it was a wrong political and/or bonus driven decision to 
> release it at a
> fixed date instead of asserting quality and completeness.
> 
> We will see what kind of nasty compromises will be necessary to avoid 
> breaking binary
> compatibility and if Qt will replace one evil with another by doing so.


The decision to release a reduced set of base modules first, and to follow up 
with functionality that is not part of the core of Qt over time, has been a 
good call, I think. Feature completeness was never the goal for Qt 6.0, and I 
don’t think it makes Qt 6(.0) a cripple, even though many projects will not be 
able to start porting until later. That’s ok, and was discussed and accepted 
during the last Qt Contributors Summit as well.

And asserting quality is not just a function of time either. The fact that we 
have all actively developed against the dev branches helped us discover issues 
early, and allowed us to fix them reasonably quickly. I personally think (and 
yes I’m biased, being the one pushing for moving away from the forward-merging 
way of operating) this has been a bigger contribution to quality and stability 
than another month or two of beta phase with very limited activity by the same 
small number of contributors and testers.


It seems that releasing a 6.0 was the best way to get more eyes and brains on 
Qt 6. Note that not breaking binary is a primarily political decision (esp if 
6.0 is indeed a cripple and can’t be used by anyone for anything meaningful). 
And if that prevents us from taking the feedback that we can apparently not get 
via betas and RCs into account, then it’s just as bad as a bonus-driven release 
timeline would be.

FWIW, as I see it, the issues that have so far been raised as BiC-candidates 
[1] are IMHO not justifying breaking binary compatibility unless we really 
really want to. Valid objections have been raised in the respective thread.

Cheers,
Volker


[1] https://bugreports.qt.io/browse/QTBUG-89157


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Alejandro Exojo]

On Mon, Jan 4, 2021, at 2:13 PM, Oswald Buddenhagen wrote:
> https://bugreports.qt.io/browse/QTQAINFRA-4121 for anyone interested in 
> the inevitable community fork.

FWIW, I created https://github.com/qt-lts-community a while ago in preparation 
for this (though I did not think much of this, TBH, I think Gitlab is maybe 
more liked by other parties). Let me know if someone is interested in using 
that Github Organization.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Tuukka Turunen]

Hi Nico,

Basic “rule of thumb” is that if a commercial Qt license holder has access to 
Qt 5.15 in general, s/he also gets Qt 5.15.3 provided that the license is 
active at the time of Qt 5.15.3 release.

Yours,

Tuukka

From: Wallmeier, Nico 
Date: Monday, 4. January 2021 at 17.33
To: Tuukka Turunen , Qt Development ML 

Subject: RE: [Development] Commercial-only LTS phase starts: Closing the 5.15 
branch(es) on 5th January
Hi Tukka,

what do you mean by “commercial only” exactly? Is Qt 5.15.3 only included in 
the subscription or is it also included in an active perpetual license?

Kind regards,
Nico Wallmeier

From: Development  On Behalf Of Tuukka 
Turunen
Sent: Montag, 4. Januar 2021 15:57
To: Roland Winklmeier ; Qt Development ML 

Subject: Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 
branch(es) on 5th January


Hi Roland,

Just so that there is no misunderstanding Qt 5.15.2 release stays available for 
all users, it is just the upcoming LTS phase patch releases that will be 
commercial only. In essence for the open-source users Qt 5.15 is similar to Qt 
5.13 and Qt 5.14 (non-LTS releases).

Yours,

Tuukka

From: Development 
mailto:development-boun...@qt-project.org>>
Date: Monday, 4. January 2021 at 16.33
To: Qt Development ML 
mailto:development@qt-project.org>>
Subject: Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 
branch(es) on 5th January
Am Mo., 4. Jan. 2021 um 14:38 Uhr schrieb Benjamin TERRIER 
mailto:b.terr...@gmail.com>>:


On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen 
mailto:oswald.buddenha...@gmx.de>> wrote:
On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
>With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming
>soon, it is time to enter the commercial-only LTS phase for Qt 5.15
>LTS.
>
that's some brilliant timing, given that no actual qt 6 release even
exists yet. (yeah, 6.0 is a joke given that you intend to break binary
compat in 6.1 - that's the wisdom of linking r's bonus payments to
release dates even for major versions).

Yes, it would have made sense that the Qt Company waits for all modules to be 
available in Qt 6 before dropping the 5.15 open support...

I cannot express how much I agree to this. Qt6 has half of the modules required 
by my project not yet available, so upgrading is not possible. On the other 
hand, 5.15 LTS is closed for the open source users - this is quite a heavy 
restriction for me since my project is non-profit and open source. Buying a 
commercial license is not an option.
Yes I'm aware that I'm a small fish in a large pond and QtC won't care about my 
contributions or me as a developer using Qt since there is no profit to make 
with me. On the other hand, I will carefully think about using Qt again in 
future projects or recommend it to other people.
This is not a complaint. Its your business and your rules. I'm just trying to 
express the thoughts of a bigger but usally silent group of open 
source/non-profit users which are directly impacted by this.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Roland Winklmeier]

Am Mo., 4. Jan. 2021 um 15:57 Uhr schrieb Tuukka Turunen <
tuukka.turu...@qt.io>:

>
>
> Hi Roland,
>
>
>
> Just so that there is no misunderstanding Qt 5.15.2 release stays
> available for all users, it is just the upcoming LTS phase patch releases
> that will be commercial only. In essence for the open-source users Qt 5.15
> is similar to Qt 5.13 and Qt 5.14 (non-LTS releases).
>

 Tuukka,

I'm aware of that, but the upcoming LTS phase patch releases are exactly
what I need. If there was a bug in the last 5.13 release, I could upgrade
to 5.14.{0,1} which typically included the fixes after the last 5.13
release. Qt6 does not yet include many important modules, so I have nothing
to upgrade to until 6.1 or 6.2.
Also not every open source project is interested to track the bleeding edge
releases, but I was rather interested in stability, hence following LTS
releases.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Benjamin TERRIER]

Le lun. 4 janv. 2021 à 15:57, Tuukka Turunen  a
écrit :

>
>
> Hi Roland,
>
>
>
> Just so that there is no misunderstanding Qt 5.15.2 release stays
> available for all users, it is just the upcoming LTS phase patch releases
> that will be commercial only. In essence for the open-source users Qt 5.15
> is similar to Qt 5.13 and Qt 5.14 (non-LTS releases).
>

It's not the same because when 5.13 and 5.14 support was dropped, 5.14 and
5.15 were released.

Now even if 6.0 is officially released, a lot of modules are not yet
released and won't be available before 6.1 or 6.2 is released.

A lot of open source users are blocked, having no patch releases for 5.15
and no way to use Qt 6 yet.

>
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Benjamin TERRIER]

Le lun. 4 janv. 2021 à 16:06, Calogero Mauceri  a
écrit :

> As far as I understand the next LTS release will be Qt 6.2.
> If 5.15 will not receive any more patches open source users are left
> without LTS till 6.2 is released. Am I correct?
>
> From now on, will LTS releases be available only for commercial users?
>

Yes. LTS is a commercial only thing now.
So Qt 6.2 will be LTS only for commercial users.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Calogero Mauceri]

As far as I understand the next LTS release will be Qt 6.2.
If 5.15 will not receive any more patches open source users are left
without LTS till 6.2 is released. Am I correct?

>From now on, will LTS releases be available only for commercial users?

Thanks,
Calogero

On Mon, Jan 4, 2021 at 3:59 PM Tuukka Turunen  wrote:

>
>
> Hi Roland,
>
>
>
> Just so that there is no misunderstanding Qt 5.15.2 release stays
> available for all users, it is just the upcoming LTS phase patch releases
> that will be commercial only. In essence for the open-source users Qt 5.15
> is similar to Qt 5.13 and Qt 5.14 (non-LTS releases).
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> *From: *Development 
> *Date: *Monday, 4. January 2021 at 16.33
> *To: *Qt Development ML 
> *Subject: *Re: [Development] Commercial-only LTS phase starts: Closing
> the 5.15 branch(es) on 5th January
>
> Am Mo., 4. Jan. 2021 um 14:38 Uhr schrieb Benjamin TERRIER <
> b.terr...@gmail.com>:
>
>
>
>
>
> On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen 
> wrote:
>
> On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
> >With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming
> >soon, it is time to enter the commercial-only LTS phase for Qt 5.15
> >LTS.
> >
> that's some brilliant timing, given that no actual qt 6 release even
> exists yet. (yeah, 6.0 is a joke given that you intend to break binary
> compat in 6.1 - that's the wisdom of linking r's bonus payments to
> release dates even for major versions).
>
>
>
> Yes, it would have made sense that the Qt Company waits for all modules to
> be available in Qt 6 before dropping the 5.15 open support...
>
>
>
> I cannot express how much I agree to this. Qt6 has half of the modules
> required by my project not yet available, so upgrading is not possible. On
> the other hand, 5.15 LTS is closed for the open source users - this is
> quite a heavy restriction for me since my project is non-profit and open
> source. Buying a commercial license is not an option.
>
> Yes I'm aware that I'm a small fish in a large pond and QtC won't care
> about my contributions or me as a developer using Qt since there is no
> profit to make with me. On the other hand, I will carefully think about
> using Qt again in future projects or recommend it to other people.
>
> This is not a complaint. Its your business and your rules. I'm just trying
> to express the thoughts of a bigger but usally silent group of open
> source/non-profit users which are directly impacted by this.
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
>


-- 
Calogero Mauceri
Software Engineer

Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Tuukka Turunen]

Hi Roland,

Just so that there is no misunderstanding Qt 5.15.2 release stays available for 
all users, it is just the upcoming LTS phase patch releases that will be 
commercial only. In essence for the open-source users Qt 5.15 is similar to Qt 
5.13 and Qt 5.14 (non-LTS releases).

Yours,

Tuukka

From: Development 
Date: Monday, 4. January 2021 at 16.33
To: Qt Development ML 
Subject: Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 
branch(es) on 5th January
Am Mo., 4. Jan. 2021 um 14:38 Uhr schrieb Benjamin TERRIER 
mailto:b.terr...@gmail.com>>:


On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen 
mailto:oswald.buddenha...@gmx.de>> wrote:
On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
>With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming
>soon, it is time to enter the commercial-only LTS phase for Qt 5.15
>LTS.
>
that's some brilliant timing, given that no actual qt 6 release even
exists yet. (yeah, 6.0 is a joke given that you intend to break binary
compat in 6.1 - that's the wisdom of linking r's bonus payments to
release dates even for major versions).

Yes, it would have made sense that the Qt Company waits for all modules to be 
available in Qt 6 before dropping the 5.15 open support...

I cannot express how much I agree to this. Qt6 has half of the modules required 
by my project not yet available, so upgrading is not possible. On the other 
hand, 5.15 LTS is closed for the open source users - this is quite a heavy 
restriction for me since my project is non-profit and open source. Buying a 
commercial license is not an option.
Yes I'm aware that I'm a small fish in a large pond and QtC won't care about my 
contributions or me as a developer using Qt since there is no profit to make 
with me. On the other hand, I will carefully think about using Qt again in 
future projects or recommend it to other people.
This is not a complaint. Its your business and your rules. I'm just trying to 
express the thoughts of a bigger but usally silent group of open 
source/non-profit users which are directly impacted by this.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt 6.0.x releasing and Qt 6.0.x changes files

[Edward Welbourne]

Jani Heikkinen (22 December 2020 09:29)
> Lars made a new proposal, see his comment in
> https://codereview.qt-project.org/c/qt/qtbase/+/324440
>
> Basic idea would be
>* We will create one release note for the release instead of
>  separate changes file in each submodule
>* Release notes are stored in separate release notes git
>  repository. That way we can freeze Qt release content & generate
>  (and finalize) release notes after the content freeze
>* We will remove dist/ folder in our current repos
>
> All that would be doable also in Qt 6.0.1 schedule (except of fully
> automated release note generation but that can be solved independently
> later) so at least I will support this Lars proposal. Any comments?

Sounds like a candidate for write-up as QUIP 20.
Any volunteers ?

Eddy.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Volker Hilsheimer]

> On 4 Jan 2021, at 15:33, Bernhard Lindner  wrote:
> 
> 
>> yeah, 6.0 is a joke given that you intend to break binary 
>> compat in 6.1 - that's the wisdom of linking r's bonus payments to 
>> release dates even for major versions
> 
> Thank you for saying what no one else dared to say.


I’m not aware of a decision to break binary compatibility in Qt 6.1. The - so 
far - last email to the respective discussion thread is

https://lists.qt-project.org/pipermail/development/2020-December/040763.html

and neither that nor any of the previous emails are conclusively stating that 
we do or don’t break BC.

The topic in this particular thread is controversial enough as it is, let’s 
stick to the facts :)

Cheers,
Volker


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Bernhard Lindner]

> yeah, 6.0 is a joke given that you intend to break binary 
> compat in 6.1 - that's the wisdom of linking r's bonus payments to 
> release dates even for major versions

Thank you for saying what no one else dared to say.

-- 
Best Regards,
Bernhard Lindner

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Roland Winklmeier]

Am Mo., 4. Jan. 2021 um 14:38 Uhr schrieb Benjamin TERRIER <
b.terr...@gmail.com>:

>
>
> On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen 
> wrote:
>
>> On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
>> >With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming
>> >soon, it is time to enter the commercial-only LTS phase for Qt 5.15
>> >LTS.
>> >
>> that's some brilliant timing, given that no actual qt 6 release even
>> exists yet. (yeah, 6.0 is a joke given that you intend to break binary
>> compat in 6.1 - that's the wisdom of linking r's bonus payments to
>> release dates even for major versions).
>>
>>
> Yes, it would have made sense that the Qt Company waits for all modules to
> be available in Qt 6 before dropping the 5.15 open support...
>

I cannot express how much I agree to this. Qt6 has half of the modules
required by my project not yet available, so upgrading is not possible. On
the other hand, 5.15 LTS is closed for the open source users - this is
quite a heavy restriction for me since my project is non-profit and open
source. Buying a commercial license is not an option.
Yes I'm aware that I'm a small fish in a large pond and QtC won't care
about my contributions or me as a developer using Qt since there is no
profit to make with me. On the other hand, I will carefully think about
using Qt again in future projects or recommend it to other people.
This is not a complaint. Its your business and your rules. I'm just trying
to express the thoughts of a bigger but usally silent group of open
source/non-profit users which are directly impacted by this.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Benjamin TERRIER]

On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen 
wrote:

> On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
> >With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming
> >soon, it is time to enter the commercial-only LTS phase for Qt 5.15
> >LTS.
> >
> that's some brilliant timing, given that no actual qt 6 release even
> exists yet. (yeah, 6.0 is a joke given that you intend to break binary
> compat in 6.1 - that's the wisdom of linking r's bonus payments to
> release dates even for major versions).
>
>
Yes, it would have made sense that the Qt Company waits for all modules to
be available in Qt 6 before dropping the 5.15 open support...

Also some patches have already been merged between the 5.15.2 and today. I
am thinking about this one in particular:
https://bugreports.qt.io/browse/QTBUG-88688
which is a regression from 5.15.1.
I find it kind of weird to release 5.15.2 let some patches in and then lock
the branches in the middle of the 5.15.3 development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Oswald Buddenhagen]

On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming 
soon, it is time to enter the commercial-only LTS phase for Qt 5.15 
LTS.


that's some brilliant timing, given that no actual qt 6 release even 
exists yet. (yeah, 6.0 is a joke given that you intend to break binary 
compat in 6.1 - that's the wisdom of linking r's bonus payments to 
release dates even for major versions).


https://bugreports.qt.io/browse/QTQAINFRA-4121 for anyone interested in 
the inevitable community fork.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Tuukka Turunen]

Hi,

This is well understandable and expected. The Qt Company is prepared to handle 
the Qt 5.15 LTS phase work. I wanted to ask if there is interest, as there may 
be some external maintainers who are interested in what goes into the 
commercial-only LTS releases e.g. due to having customers using those.

Yours,

Tuukka

From: Development 
Date: Monday, 4. January 2021 at 15.01
To: Qt development mailing list 
Subject: Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 
branch(es) on 5th January
Tend to agree with Thiago.
If there is a decision to close 5.15 sources, there'll be no more work from 
external/unpaid contributors.

Regards,
Konstantin


пн, 4 янв. 2021 г. в 15:21, Thiago Macieira 
mailto:thiago.macie...@intel.com>>:
On Monday, 4 January 2021 07:55:03 -03 Tuukka Turunen wrote:
> We can arrange access for external module maintainers to the commercial-only
> repositories. If there is interest, please contact me or Tarja Sundqvist
> tarja.sundqv...@qt.io>
>  who is the release
> manager for the commercial-only LTS releases.

There is no interest in on part.

That means I will not be participating in the development of those fixes,
commenting on what's appropriate or not, reviewing backports, or bug reports.
In fact, bug reports that cannot be reproduced on 6.0 will also be closed.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Konstantin Ritt]

Tend to agree with Thiago.
If there is a decision to close 5.15 sources, there'll be no more work from
external/unpaid contributors.

Regards,
Konstantin


пн, 4 янв. 2021 г. в 15:21, Thiago Macieira :

> On Monday, 4 January 2021 07:55:03 -03 Tuukka Turunen wrote:
> > We can arrange access for external module maintainers to the
> commercial-only
> > repositories. If there is interest, please contact me or Tarja Sundqvist
> > tarja.sundqv...@qt.io who is the release
> > manager for the commercial-only LTS releases.
>
> There is no interest in on part.
>
> That means I will not be participating in the development of those fixes,
> commenting on what's appropriate or not, reviewing backports, or bug
> reports.
> In fact, bug reports that cannot be reproduced on 6.0 will also be closed.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel DPG Cloud Engineering
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
>
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Thiago Macieira]

On Monday, 4 January 2021 07:55:03 -03 Tuukka Turunen wrote:
> We can arrange access for external module maintainers to the commercial-only
> repositories. If there is interest, please contact me or Tarja Sundqvist
> tarja.sundqv...@qt.io who is the release
> manager for the commercial-only LTS releases.

There is no interest in on part.

That means I will not be participating in the development of those fixes, 
commenting on what's appropriate or not, reviewing backports, or bug reports. 
In fact, bug reports that cannot be reproduced on 6.0 will also be closed.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

[Tuukka Turunen]

Hi,

With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming soon, it 
is time to enter the commercial-only LTS phase for Qt 5.15 LTS. All the 
existing 5.15 branches remain publicly visible, but they are closed for new 
commits (and cherry-picks). Exception being the Qt WebEngine (and the 
deprecated Qt Script), which have a 3rd party LGPL dependency.

Closing happens tomorrow, 5th January 2021. After this the cherry-picks go to 
another repository that will be available only for the commercial license 
holders. We will arrange repository access to the commercial license holders, 
so in addition to the official releases it is possible to use the repositories. 
Instructions about this will be available to commercial license holders during 
next week, after we have completed the license change and other preparations.

First commercial-only Qt 5.15.3 LTS patch release is planned to be released in 
February.

We can arrange access for external module maintainers to the commercial-only 
repositories. If there is interest, please contact me or Tarja Sundqvist 
tarja.sundqv...@qt.io who is the release manager 
for the commercial-only LTS releases.

Yours,

Tuukka



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Max Goldstein as an approver

[Alex Blasche]

Congrats to Max, approver rights have been granted.

--
Alex


From: Development  on behalf of Fabian 
Kosmale 
Sent: Monday, 14 December 2020 09:28
To: Ulf Hermann; development@qt-project.org
Subject: Re: [Development] Nominating Max Goldstein as an approver

+ 1

Max also didn't shy away from diving into the lesser known parts of 
qtdeclarative like qv4codegen.cpp when adding support nullish coalescing. I'm 
sure he'll be a responsible approver.

The usual disclosure regarding  team and office applies.

--
Fabian Kosmale
Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin
fabian.kosm...@qt.io
+49 1638686070
http://qt.io


Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

--


Von: Development  im Auftrag von Ulf 
Hermann 
Gesendet: Montag, 14. Dezember 2020 09:13
An: development@qt-project.org
Betreff: [Development] Nominating Max Goldstein as an approver

Hi,

I would like to nominate Max Goldstein as an approver for the Qt Project.

Max has been contributing to the Qt project for a while now. He wrote
the qmlformat tool, implemented the JavaScript URL object for QML, and
contributed to pyside.

Here is the list of his changes on gerrit:
https://codereview.qt-project.org/q/owner:max.goldstein%2540qt.io

Disclaimer: I'm working in the same area and if we weren't working from
home we'd share an office.

best regards,
Ulf
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development