Re: [Development] Qt 6.2.6 LTS Commercial released

2022-09-28 Thread Jaroslaw Kobus
Wow!

This thread already generated 12 messages - this one is the 13th. How many 
possible future commercial release e-mails could substitute all the posts from 
this thread? Would we be around 2024 already or later, isn't it?

Is there really no bigger problem in the cruel world right now these days than 
wondering whether the sent e-mail with info about commercial release can or 
can't be filtered conveniently enough out by interested people?

How many of subscribers receive this e-mail thread and feel much more 
uncomfortable with this thread comparing to the rare info about commercial 
release (unwanted by some, apparently wanted by others)?

Keep safe!

Jarek


From: Development  on behalf of Albert 
Astals Cid 
Sent: Wednesday, September 28, 2022 9:58 PM
To: development@qt-project.org
Subject: Re: [Development] Qt 6.2.6 LTS Commercial released

El dimecres, 28 de setembre de 2022, a les 21:23:57 (CEST), Lorn Potter va
escriure:
> On 27/9/2022 9:28 pm, Konstantin Ritt wrote:
> > Please stop announcing this kind of updates through the development
> > mailing list!
>
> Please do *not* stop sending releasing information emails on this list.
> I kinda like knowing about them.
>
> Release information, regardless of open source or commercial licensing,
> is relevant to Qt development, even if you are an open source purist
> and/or understand the realities of the software industry.

If you want to learn about release announcements of Qt, you should subscribe
to the list that precisely is about release announcements of Qt.

https://lists.qt-project.org/listinfo/announce

Best Regards,
  Albert



___
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] Qt 6.2.6 LTS Commercial released

2022-09-28 Thread Albert Astals Cid
El dimecres, 28 de setembre de 2022, a les 21:23:57 (CEST), Lorn Potter va 
escriure:
> On 27/9/2022 9:28 pm, Konstantin Ritt wrote:
> > Please stop announcing this kind of updates through the development
> > mailing list!
> 
> Please do *not* stop sending releasing information emails on this list.
> I kinda like knowing about them.
> 
> Release information, regardless of open source or commercial licensing,
> is relevant to Qt development, even if you are an open source purist
> and/or understand the realities of the software industry.

If you want to learn about release announcements of Qt, you should subscribe 
to the list that precisely is about release announcements of Qt.

https://lists.qt-project.org/listinfo/announce

Best Regards,
  Albert



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


Re: [Development] Qt 6.2.6 LTS Commercial released

2022-09-28 Thread Lorn Potter


On 27/9/2022 9:28 pm, Konstantin Ritt wrote:
Please stop announcing this kind of updates through the development 
mailing list!



Please do *not* stop sending releasing information emails on this list. 
I kinda like knowing about them.


Release information, regardless of open source or commercial licensing, 
is relevant to Qt development, even if you are an open source purist 
and/or understand the realities of the software industry.


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


Re: [Development] Qt 6.2.6 LTS Commercial released

2022-09-28 Thread Elvis Stansvik
Yea apologies, when I said not a big deal, I meant not a big deal to me
personally. Should have been clearer.

Elvis

Den ons 28 sep. 2022 00:51Konstantin Ritt  skrev:

> Ignoring a large part of the community IS a problem.
> Most people won't say they aren't ok with something. Until it is too late
> to say anything at all.
>
> Regards,
> Konstantin
>
>
> вт, 27 сент. 2022 г. в 23:02, Elvis Stansvik :
>
>> Den tis 27 sep. 2022 kl 21:52 skrev Elvis Stansvik :
>> >
>> > Den tis 27 sep. 2022 kl 21:01 skrev Thiago Macieira <
>> thiago.macie...@intel.com>:
>> > >
>> > > On Tuesday, 27 September 2022 09:48:01 PDT Elvis Stansvik wrote:
>> > > > The typical mail here is about development of Qt, and while some of
>> > > > those mails may be specialized and only may not be interesting to
>> > > > *everyone*, they could potentially be interesting to *anyone* (e.g.
>> > > > cover some technical topic they want to learn about etc). I don't
>> > > > think that can be said of commercial-only release announcement,
>> which
>> > > > are for sure only interesting to a certain subset of subscribers, so
>> > > > suggest keeping them on some commercial-only list.
>> > >
>> > > For me, what's interesting is to know the *date* of the release,
>> because it
>> > > sets the 12-month timer for a new open source drop.
>> >
>> > True :)
>> >
>> > Open source code drops can be announced here, but I guess there's some
>> > value in knowing about the first commercial-only releases, for those
>> > who want to pencil in the drop date in their calendars.
>>
>> I guess it's just that I can understand Konstantin's sentiment, since
>> it feels kind of unsolicited. When I signed up for this list, I
>> solicited Qt development conversations. There is a list for
>> announcements after all. It feels like I'm getting a newsletter I
>> didn't sign up for, without a way to unsubscribe without losing all
>> the Qt dev conversations that I do want to follow.
>>
>> But if most people are OK with it, no problem. It's not a big deal.
>>
>> Elvis
>>
>> >
>> > Elvis
>> >
>> > >
>> > > --
>> > > Thiago Macieira - thiago.macieira (AT) intel.com
>> > >   Cloud Software Architect - Intel DCAI 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
>>
>
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Qt 6.2.6 LTS Commercial released

2022-09-28 Thread Allan Sandfeld Jensen
On Mittwoch, 28. September 2022 10:31:52 CEST Volker Hilsheimer wrote:
> > On 27 Sep 2022, at 22:01, Elvis Stansvik  wrote:
> > 
> > Den tis 27 sep. 2022 kl 21:52 skrev Elvis Stansvik :
> >> Den tis 27 sep. 2022 kl 21:01 skrev Thiago Macieira 
:
> >>> On Tuesday, 27 September 2022 09:48:01 PDT Elvis Stansvik wrote:
>  The typical mail here is about development of Qt, and while some of
>  those mails may be specialized and only may not be interesting to
>  *everyone*, they could potentially be interesting to *anyone* (e.g.
>  cover some technical topic they want to learn about etc). I don't
>  think that can be said of commercial-only release announcement, which
>  are for sure only interesting to a certain subset of subscribers, so
>  suggest keeping them on some commercial-only list.
> >>> 
> >>> For me, what's interesting is to know the *date* of the release, because
> >>> it
> >>> sets the 12-month timer for a new open source drop.
> >> 
> >> True :)
> >> 
> >> Open source code drops can be announced here, but I guess there's some
> >> value in knowing about the first commercial-only releases, for those
> >> who want to pencil in the drop date in their calendars.
> > 
> > I guess it's just that I can understand Konstantin's sentiment, since
> > it feels kind of unsolicited. When I signed up for this list, I
> > solicited Qt development conversations. There is a list for
> > announcements after all. It feels like I'm getting a newsletter I
> > didn't sign up for, without a way to unsubscribe without losing all
> > the Qt dev conversations that I do want to follow.
> > 
> > But if most people are OK with it, no problem. It's not a big deal.
> > 
> > Elvis
> 
> Ok; we have annou...@qt-project.org specifically for announcing releases, so
> we'll send all future release announcements only to that list, without any
> cross-posting to development@qt-project.org.
> 
> 
All of them, or only the LTS ones? It seems most people didn't mind the open 
source announcements here.

Best regards
Allan


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


Re: [Development] Qt 6.2.6 LTS Commercial released

2022-09-28 Thread Volker Hilsheimer
> On 27 Sep 2022, at 22:01, Elvis Stansvik  wrote:
> Den tis 27 sep. 2022 kl 21:52 skrev Elvis Stansvik :
>> 
>> Den tis 27 sep. 2022 kl 21:01 skrev Thiago Macieira 
>> :
>>> 
>>> On Tuesday, 27 September 2022 09:48:01 PDT Elvis Stansvik wrote:
 The typical mail here is about development of Qt, and while some of
 those mails may be specialized and only may not be interesting to
 *everyone*, they could potentially be interesting to *anyone* (e.g.
 cover some technical topic they want to learn about etc). I don't
 think that can be said of commercial-only release announcement, which
 are for sure only interesting to a certain subset of subscribers, so
 suggest keeping them on some commercial-only list.
>>> 
>>> For me, what's interesting is to know the *date* of the release, because it
>>> sets the 12-month timer for a new open source drop.
>> 
>> True :)
>> 
>> Open source code drops can be announced here, but I guess there's some
>> value in knowing about the first commercial-only releases, for those
>> who want to pencil in the drop date in their calendars.
> 
> I guess it's just that I can understand Konstantin's sentiment, since
> it feels kind of unsolicited. When I signed up for this list, I
> solicited Qt development conversations. There is a list for
> announcements after all. It feels like I'm getting a newsletter I
> didn't sign up for, without a way to unsubscribe without losing all
> the Qt dev conversations that I do want to follow.
> 
> But if most people are OK with it, no problem. It's not a big deal.
> 
> Elvis


Ok; we have annou...@qt-project.org specifically for announcing releases, so 
we'll send all future release announcements only to that list, without any 
cross-posting to development@qt-project.org.


Volker

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


[Development] Meeting minutes from Qt Release Team meeting 27.09.2022

2022-09-28 Thread Jani Heikkinen
Qt 6.4 status:
   - Qt 6.4.0 release content frozen & release packages created
  * RTA ongoing
 - We will release these packages as Qt 6.4.0 Thu 29th September 2022

Confirmed Qt 6.5 schedule:
   * Qt 6.5 Platform and Module freeze: 25th November 2022
   * Qt 6.5 Feature Freeze: 9th December 2022
   * Qt 6.5 Beta1: 15th December 2022
   * Qt 6.5 RC: 16th March 2023
   * Qt 6.5.0 Final release 30th March 2023

Next meeting Tue 11th October 2022 16:00 CET

br,
Jani Heikkinen
Release Manager 

irc log below: 
[17:01:07] <+jaheikki3> akseli: ablasche: carewolf_home: frkleint: 
lars_:mapaaso:The-Compiler:thiago:vohi: ping
[17:01:12]  pong
[17:01:17]  jaheikki3: pong
[17:01:25]  pong
[17:01:51] <+jaheikki3> Time to start Qt release team meeting
[17:01:55] <+jaheikki3> On agenda today:
[17:02:00] <+jaheikki3> Qt 6.4 status
[17:02:12] <+jaheikki3> Qt 6.5 schedule
[17:02:21] <+jaheikki3> Any additional item to the agenda?
[17:04:03] <+jaheikki3> Ok, let's start from Qt 6.4 status
[17:04:30] <+jaheikki3> QT 6.4.0 final content was frozen and testing is ongoing
[17:05:15] <+jaheikki3> unfortunately @kkoehne just reported 
https://bugreports.qt.io/browse/QTBUG-107007 and we think we need to fix that 
one for .0 as well
[17:05:53] <+jaheikki3> So we will take this one in & create new packages asap
[17:05:56]  Is it top configuration? Seems like the kind of 
thing we could update later
[17:06:33] <+jaheikki3> well, not sure
[17:07:05] <+jaheikki3> But maybe it isn't, it seems we don't have that in our 
CI or other tests
[17:07:21]  agree, as long as qtbase can be configured with -no-gui this 
is acceptable, I think
[17:07:26]  well, our CI don't do top-level build but build per 
module
[17:08:33]  oh, well not a big problem either :shrug:
[17:08:56]  I wouldn't even call -no-gui a showstopper
[17:09:14]  Perhaps enough to have that added to release-test-automation 
coverage; but I don't think this should stop the show, there are ways to 
exclude submodules that are very obviously depending on GUI
[17:09:58] <+jaheikki3> Ok, lets then keep this as known issue for Qt 6.4.0 and 
get the fix in 6.4.1
[17:10:29] <+jaheikki3> And of course improve our test to catch this kind of 
issues earlier
[17:10:59] <+jaheikki3> So we will release existing packages as Qt 6.4.0 Thu 
29th September as planned
[17:11:04]  not sure we want top-level build steps in 
integration testing, that takes too long
[17:12:16] <+jaheikki3> carewolf_home: yeah, we need to plan to where to add 
this new test
[17:12:45]  RTA is enough I think, and top-level build testing the source 
package that we include in the downloads is a good idea anyway, if that's not 
already done. Not sure that -no-gui is a priority though :)
[17:13:41] <+jaheikki3> Yeah, agree. There is something already in RTA but I'll 
check with johanna if this could be something to be added
[17:13:45] <+jaheikki3> But it was all about Qt 6.4 status at this time. Any 
more comments or questions?
[17:13:46]  I always wanted a lazy tester in the background 
randomly building with different combinations on and off, and opening bugs when 
failing something
[17:13:55]  no, questions
[17:15:26] <+jaheikki3> Ok, then Qt schedule
[17:16:08] <+jaheikki3> In last meeting minutes I proposed the schedule for 
6.5, see 
https://lists.qt-project.org/pipermail/development/2022-September/042983.html
[17:16:29] <+jaheikki3> There weren't any objections so the initial schedule 
for Qt 6.5 will be 
[17:16:51] <+jaheikki3> * Qt 6.5 Platform and Module freeze: 25th November 2022
[17:16:51] <+jaheikki3> * Qt 6.5 Feature Freeze: 9th December 2022
[17:16:51] <+jaheikki3> * Qt 6.5 Beta1: 15th December 2022
[17:16:51] <+jaheikki3> * Qt 6.5 RC: 16th March 2023
[17:16:51] <+jaheikki3> * Qt 6.5.0 Final release 30th March 2023
[17:18:03] <+jaheikki3> I think it was all at this time.
[17:18:42] <+jaheikki3> Let's skip next week's meeting and have new one Tue 
11th October at this same time
[17:18:57]  bye
[17:18:59] <+jaheikki3> Thanks for your participation, bye!
[17:19:06]  thanks, bye!
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development