Re: [Development] HEADS-UP: Qt 6.10 Feature Freeze

Hi, We should have snapshots of Qt 6.11 (dev) available also before the release of Qt 6.10, so as soon as the functionality is ready enough to be tried out that can be done also using Qt 6.11 snapshot. The challenge of course is how to find the ones to try out things in a pre-release as it is n

Re: [Development] Proposing QUIP-23: Qt-Security header in source code files

Hi, Yes, exactly that (untrusted input) and especially the parts where this is done by Qt (so that it is not even possible for the app to check etc). There might be some other ones as well, but main idea is to separate those few places where extra good care must be taken from the baseline (whic

Re: [Development] Fwd: Removing Qt 3D from release configuration in dev branch

/+/246320 Yours, Tuukka From: Björn Strömberg Date: Thursday, March 28, 2024 at 10:06 To: Tuukka Turunen Cc: Qt Project Development , Qt3D-Dev Subject: Re: [Development] Fwd: Removing Qt 3D from release configuration in dev branch Hello Tuukka, thanks for your answer. In my

Re: [Development] Fwd: Removing Qt 3D from release configuration in dev branch

>> Date: Thu, Mar 28, 2024 at 2:53 AM Subject: Re: [Development] Removing Qt 3D from release configuration in dev branch To: Tuukka Turunen mailto:tuukka.turu...@qt.io>> So now qt-6.x is effecively only promise backwards-compatible module wise to 6.8? As written it's open to int

Re: [Development] Removing Qt 3D from release configuration in dev branch

From: Development on behalf of Giuseppe D'Angelo via Development Date: Wednesday, March 27, 2024 at 14:30 To: development@qt-project.org Subject: Re: [Development] Removing Qt 3D from release configuration in dev branch Hi, On 27/03/2024 09:39, Tuukka Turunen via Development wrote: &

[Development] Removing Qt 3D from release configuration in dev branch

Hi, We have been discussing with KDAB about the future maintenance of Qt 3D module. It is a quite large and complex module, which has for most use cases by now been superseded by Qt Quick 3D. Since Qt 3D has been available for a long time, it should continue to be available for those who still

Re: [Development] Decrease amount of qt releases in online installer

Hi, For the open-source online installer where mirorbrain is used. The commercial distribution is done with a different system where mirror space is not an issue and there is a much higher number of “mirrors”, so also the archive performance is a bit better. Yours,

Re: [Development] Decrease amount of qt releases in online installer

Hi, This is a good change. It has been a long time since we previously cleaned the releases available via the online installer, so the number has been growing to be quite large. In general we should be always guiding users towards the latest releases and to large extent users are doing that. W

[Development] Update What's new in Qt 6.7 (Was: Re: HEADS-UP: Qt 6.7 Feature Freeze)

Hi, There is quite a lot of things missing still from https://codereview.qt-project.org/c/qt/qtdoc/+/524057 Qt 6.7 Beta 1 release is somewhere early next week and we should publish the first iteration of the What’s new page along with it. Yours, Tuukka From: Development on

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

Hi, Thiago is right, we can change the name as the module technically is not part of Qt release (https://download.qt.io/official_releases/qt/6.6/6.6.1/submodules/). That said, we can also decide not to change the name. Like mentioned by Dominik, it has existing since a while with the current n

Re: [Development] Meeting minutes from Qt Release Team meeting 20.06.2023

Hi, Still on its way, there were a couple of items found during testing and new packages with those fixes needed to be built (and now new test round ongoing). Probably early next week, but anyways as soon as possible. Yours, Tuukka From: Development on behalf of Ilya Fedin

Re: [Development] Raising the minimum to C++20

Hi, I also agree that it is important to keep moving along and harness what new C++ versions offer in the best way we can. Potential time to do this would indeed be in the near future – one good point in time to drop support for older compilers could be with Qt 6.9 around March 2025 as mentione

Re: [Development] Proposal: let's change the release schedules a bit

June? Yours, Tuukka From: Tuukka Turunen Date: Wednesday, 14. December 2022 at 11.44 To: Volker Hilsheimer , Jani Heikkinen Cc: development@qt-project.org Subject: Re: [Development] Proposal: let's change the release schedules a bit Hi, One of the

Re: [Development] New Qt example development guideline and revamping examples

, Tuukka From: Development on behalf of Shawn Rutledge via Development Date: Friday, 3. February 2023 at 15.56 To: Qt Development Subject: Re: [Development] New Qt example development guideline and revamping examples On 3 Feb 2023, at 13:56, Tuukka Turunen via Development wrote: pdf

Re: [Development] New Qt example development guideline and revamping examples

Hi, …and in case unsure what is shown in docs & Creator, it is the ones listed in the manifest file as described at https://doc.qt.io/qt-6/26-qdoc-configuration-example-manifest-files.html and https://wiki.qt.io/Qt_Examples_in_Qt_Creator Mostly these are examples that have not been deemed rele

Re: [Development] New Qt example development guideline and revamping examples

Hi, Yes, intention is to improve also the application / project examples in qtdoc repo. In addition to the Qt 6 best practices, these could also get a bit of visual or functionality polish. Problematic or unnecessary existing examples could be removed. Intention is also to adjust how the exampl

Re: [Development] New Qt example development guideline and revamping examples

Hi, Typically pick to 6.5 as the examples like documentation is unproblematic to update. Yours, Tuukka From: Development on behalf of Ivan Solovev via Development Date: Wednesday, 18. January 2023 at 12.09 To: development@qt-project.org , Kimmo Leppälä Subject: Re: [Develo

Re: [Development] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops

Hi, One more thing to note related to 10.15 support in Qt 6.5 is that even if it is dropped from the supported platforms (as has been planned), it doesn’t mean it would be impossible for someone to use it in their application. Of course, deploying to an unsupported version means more testing an

Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops

-source applications. You can learn more about Qt Insight at https://www.qt.io/product/insight Yours, Tuukka Lähettäjä: Cristian Adam Lähetetty: maanantaina, joulukuuta 19, 2022 5:58 ip. Vastaanottaja: Michael Jackson ; Tuukka Turunen ; Macieira, Thiago

Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops

Hi, This mailing list thread is actually already part of the discussion. I am sure the relevant stakeholders will read though the mails. One important thing: the question is whether or not the _latest_ Qt version supports 3 or 4 generations of macOS – because we already support the older macOS

Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops

evelopment@qt-project.org ; inter...@qt-project.org Kopio: Tuukka Turunen Aihe: Re: [Interest] [Development] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops On Saturday, 17 December 2022 05:40:48 -03 Tuukka Turunen via Interest wrote: > at least between versions 10.15 and 11 there does

Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops

Hi, Most of the macOS users are quite quick to take on new OS versions and this is true also for adoption of macOS versions with the new numbering scheme. Apple hardware is also rather good in keeping support for new OS versions and at least between versions 10.15 and 11 there does not seem to

Re: [Development] Proposal: let's change the release schedules a bit

Hi, One of the main problems we face every time with the feature freeze is a lot of changes coming in just before the deadline. While this is quite natural as such, it does also cause some amount of instability and problems in getting the full integration test round completed regularly. There a

Re: [Development] Requesting Feature Freeze exception for CTF tracing backend

Hi, It would be good to have these in. Yours, Tuukka Lähettäjä: Development käyttäjän Antti Määttä via Development puolesta Lähetetty: perjantaina, joulukuuta 9, 2022 3:41 ip. Vastaanottaja: development@qt-project.org Aihe: [Development] Requesting Feature F

Re: [Development] Qt 6.2.6 LTS Commercial released

Hi, You are right that cross-posting release announcements to multiple lists might actually not be needed? These three lists (announce, release, development) are the ones often used for announcing a new release. It might be that announcing only via the announce list would be enough. For a new r

Re: [Development] Commercial-only 6.2 LTS phase starts: Closing the 6.2 branch(es) on 20th April

Hi Konstantin, I am sorry to hear that you are unhappy with Qt 6.2 moving to the commercial-only long-term-support phase with release of Qt 6.2.5. We are no holding back on bug fixes, though. All applicable bug fixes go to dev and are picked to all active branches. The fix to QTBUG-102962 was

Re: [Development] Updates on Qt Location

Hi Kevin et al, Like said in the initial mail: “Development happens in the dev branch, against the dev-branches of the rest of Qt.” So things will work at least to the extent of compilation and passing whatever tests are enforced by CI. However, as there is no intention of making an official r

Re: [Development] Proposal to delete the "Maintainers" group in gerrit

Hi, We could move the authorative maintainer list to be a QUIP instead of a Wiki page. Yours, Tuukka From: Development on behalf of Volker Hilsheimer Date: Tuesday, 28. June 2022 at 17.41 To: development@qt-project.org Subject: [Development] Proposal to delete the "Maintain

Re: [Development] Qt 5.15.10 LTS Commercial released

Hi, The release notes are stored within Qt Account (under Downloads, select Product: Qt and Version: 5.15.10), i.e. one needs to have a commercial license to see those. Yours, Tuukka From: Development on behalf of Milian Wolff via Development Date: Wednesday, 8. June 2022 a

Re: [Development] Maintainance Tool

Great to hear. Thanks for reporting the issue and verifying that authentication works now. In case someone is curious what the bug was: the login form did not disable the authentication button after it was pressed, so it was possible that multiple requests were sent to backend, which then caus

Re: [Development] Maintainance Tool

all had hoped would not occur again in Europe. We had hoped that the hard learned lessons of our grand parents would prevent this from happening. Let's at least try to be a voice of reason in this situation. Konrad On 04/03/2022 17:34, Tuukka Turunen wrote: Hi, Like already men

Re: [Development] Maintainance Tool

Hi, Like already mentioned, use of the online installer is blocked from certain IP addresses. Access to the Qt Project source code repository has not been blocked. If you wish to discuss this, please remember http://quips-qt-io.herokuapp.com/quip-0012-Code-of-Conduct.html Yours,

Re: [Development] Qt 6.2.0 RC released

Hi, We have gotten a lot of valuable feedback on the Qt 6.2 pre-releases and the RC looks very solid. There are always some things to fix, and now it is crucially important to get all feedback quickly to the release team. There is time to fix issues before the Qt 6.2.0 final, but that requires

Re: [Development] Qbs development

nce’ clause for a reason and if you have tried other means before, I can and will of course arrange such a vote. Cheers, Lars On 15 Sep 2021, at 12:18, Tuukka Turunen mailto:tuukka.turu...@qt.io>> wrote: Hi, I would not like Qbs development to move away from the Qt project. It is very

Re: [Development] Qbs development

Hi, I would not like Qbs development to move away from the Qt project. It is very unfortunate that you have had bad experience and misbehavior from one approver. We want to constantly improve the experience of working within the Qt project and naturally this kind of incidents are not doing that

Re: [Development] Qbs development

, 13. September 2021 at 23.59 To: Qt development mailing list Cc: Lars Knoll , Tuukka Turunen , Oswald Buddenhagen , Christian Kandeler Subject: Qbs development Hello everybody I would like to raise an issue about Oswald Buddenhagen abusing his maintainer rights. He is constantly blocking the

Re: [Development] API Change Review for 6.2

Hi, We have gotten review of the modules with larger number of changes progressing well, but a few modules are still without comments. With the Alpha out and Beta 1 soon ready to be released it is time to complete the API review so that we have the agreement upon what to do before release of

Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

Hi, Having the controls within declarative and also using the controls more in all the relevant examples would be beneficial for the users. So I think this might be one dependency we could add, not only for testing. Yours, Tuukka Lähettäjä: Development käytt

Re: [Development] Changes to Freenode's IRC

Hi, Before simply voting for new irc provider, I would still prefer to have the QtCS discussion on the topic. We should also discuss and define what is the intention / intentions of the channels, because this can affect the choice. If it is for contributors to discuss with each other and rele

Re: [Development] Changes to Freenode's IRC

Hi, One option (following a bit what Andy wrote below) would be to do nothing immediately, but instead discuss this in the upcoming Qt Contributor’s Summit to plan the next steps. While there is currently a lot of turmoil around freenode they have not disappeared or intend to do so (https://fr

Re: [Development] Changes to Freenode's IRC

Hi Jason, You can check the planned modules for Qt 6.2 from: https://www.qt.io/blog/qt-roadmap-for-2021 The first snapshot of Qt 6.2 does not yet contain all of those, but then again we are still some weeks (2.5) away from FF. It is ok to discuss this type of matters in the mailing list, but

Re: [Development] Commercial LTS Qt 5.15.4 released

Hi, Most of the maintainers are also addressing issues in the commercial LTS releases, including also some who do not work for The Qt Company. So in that sense it is not completely off, but I do agree that announcing the commercial LTS releases via the announce list is probably enough. Yours,

Re: [Development] Qt 6.2 Feature Freeze is getting closer...

Hi, One item to note related to feature freeze of Qt 6.2 is that due to the holiday season between FF and final we can’t have exceptions as was done e.g. for Qt 6.0 FF. So if you are working on some items that are likely to go over the FF or cut tight, these should be discussed beforehand. Not

Re: [Development] [Interest] Mac Big Sur - Qt Open-Source Support For

Hi, Supporting Apple silicon is something we are actively working to have in place for Qt 6.2 including full CI coverage etc. To some extent things will work also with Qt 5.15 if you build yourself, but there are some rough edges (and Qt 5.15 is not tested for M1). Yours, Tuuk

Re: [Development] Status of the QtFeedback module

Hi, We can increase the test coverage (e.g. additional CI configurations) and if needed it is possible to have the playground and other modules to be packaged into a ‘release’ source package. Typically users are simply pulling from the repos directly, though. If the module is not tightly coupl

[Development] Shipping additional libraries as binaries with Qt 6.1

Hi, We are planning to deliver binaries of additional libraries via the online installer starting from Qt 6.1 beta 3, i.e. revert back to the model used with Qt 5. Despite the improvements achieved with Creator 4.15 and Qt 6.1 for the package manager functionality the approach introduced with

Re: [Development] [Interest] [Releasing] download.qt.io is down

link for filing a bug for the right component: https://bugreports.qt.io/secure/CreateIssueDetails!init.jspa?pid=10510&issuetype=1&components=19211 Yours, Tuukka From: Alexandre Ribeiro Date: Wednesday, 27. January 2021 at 14.24 To: Tuukka Turunen Cc: Qt Project Dev

Re: [Development] [Interest] [Releasing] download.qt.io is down

://bugreports.qt.io/secure/CreateIssueDetails!init.jspa?pid=10510&issuetype=1&components=19211 Yours, Tuukka From: Alexandre Ribeiro Date: Wednesday, 27. January 2021 at 14.24 To: Tuukka Turunen Cc: Qt Project Development , Interests Qt Subject: Re: [Interest] [Dev

Re: [Development] [Releasing] [Interest] download.qt.io is down

: Friday, 22. January 2021 at 11.32 To: Nils Jeisecke , Tuukka Turunen , Qt Project Development Subject: Re: [Development] [Releasing] [Interest] download.qt.io is down On Fri, Jan 22, 2021 at 10:38 AM Nils Jeisecke via Development wrote: > > Hi there, > > On Fri, Jan 22, 2021 at 7:59 AM Tu

Re: [Development] [Releasing] [Interest] download.qt.io is down

16.09 To: Tuukka Turunen Cc: Qt Project Development Subject: Re: [Releasing] [Interest] download.qt.io is down Thank you for clarifying, Tuukka. I am (along with many others, I'm sure) delighted to hear about the upcoming ability to officially select mirrors, and look forward to an imp

Re: [Development] [Releasing] [Interest] download.qt.io is down

, we can start transferring the release packages to it, test that everything works and put the system back online. Yours, Tuukka From: Sze Howe Koh Date: Wednesday, 20. January 2021 at 16.09 To: Tuukka Turunen Cc: Qt Project Development Subject: Re: [Releasing] [Interest

Re: [Development] [Releasing] [Interest] download.qt.io is down

Turunen Cc: Mark Long , development@qt-project.org , Interests Qt , releas...@qt-project.org Subject: Re: [Releasing] [Interest] download.qt.io is down On Wed, 20 Jan 2021 at 04:10, Tuukka Turunen wrote: > > > Hi, > > There are multiple mirrors, try for example: >

Re: [Development] [Releasing] [Interest] download.qt.io is down

Howe Koh Date: Wednesday, 20. January 2021 at 0.10 To: Tuukka Turunen Cc: Mark Long , development@qt-project.org , Interests Qt , releas...@qt-project.org Subject: Re: [Releasing] [Interest] download.qt.io is down On Wed, 20 Jan 2021 at 04:10, Tuukka Turunen wrote: > > > Hi, >

Re: [Development] [Releasing] [Interest] download.qt.io is down

Hi, Yes, this is correct. Yours, Tuukka From: Sze Howe Koh Date: Wednesday, 20. January 2021 at 0.10 To: Tuukka Turunen Cc: Mark Long , development@qt-project.org , Interests Qt , releas...@qt-project.org Subject: Re: [Releasing] [Interest] download.qt.io is down On Wed

Re: [Development] [Interest] download.qt.io is down

: [Development] [Interest] download.qt.io is down On Tuesday, 19 January 2021 12:08:57 PST Tuukka Turunen wrote: > ...or just use the online installer, which picks mirrors automatically. Where does it get the list of mirrors from? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Archit

Re: [Development] [Interest] download.qt.io is down

Lähettäjä: Mark Long Lähetetty: tiistaina, tammikuuta 19, 2021 9:58 ip. Vastaanottaja: Tuukka Turunen Kopio: Jani Heikkinen; development@qt-project.org; releas...@qt-project.org; Interests Qt Aihe: Re: [Interest] download.qt.io is down It seems that the only mirror list I can find online is

Re: [Development] download.qt.io is down

Hi, Update on the status. The downtime is caused by severe disk system failure at our cloud service provider. The service provider has notified us that they will not be able to repair the disk systems during today. Two important servers related to open-source package delivery are affected (dow

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

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

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

: 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 +0000, 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 phas

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

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 main

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

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 (an

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

+1 From: Development Date: Tuesday, 22. December 2020 at 10.33 To: development@qt-project.org Subject: Re: [Development] Qt 6.0.x releasing and Qt 6.0.x changes files Hi, Lars made a new proposal, see his comment in https://codereview.qt-project.org/c/qt/qtbase/+/324440 Basic idea would be

Re: [Development] Qt 6.0 RC and timelines for 6.1 and 6.2

Hi, Qt 6.2 would be the one that becomes long-term supported (for commercial license holders) when we keep the cadence of every 3rd release. Yours, Tuukka From: Development Date: Sunday, 29. November 2020 at 20.41 To: development@qt-project.org Subject: Re: [Development] Qt

Re: [Development] Building additional components with Conan for Qt 6

Hi Richard, Like Iikka wrote the primary plan is to leverage package manager to make it easier to work with additional components. We now have two Qt add-ons (Qt Network Authorization and Qt Image Formats) to test with. Our thinking is that the Qt installer is still the way to get the baseline

Re: [Development] Feature freeze next Tuesday

Hi, Do you have some estimate how long time is needed to get these in? Also, do you foresee any issues these changes may cause to others? Yours, Tuukka On 1.9.2020, 11.01, "Development on behalf of Giuseppe D'Angelo via Development" wrote: Il 26/08/20 08:46, Lars Knoll ha scr

Re: [Development] Codereview maintenance break is over

Hi, Thanks! That was fast. Codereview seems to be working nicely with the new version. Yours, Tuukka From: Development on behalf of Jukka Jokiniva Date: Monday 24. August 2020 at 8.19 To: Qt Project Development Subject: [Development] Codereview maintenance b

Re: [Development] Can your module be included in Qt 6?

Hi Ekke, We also have new installer cooking up for Qt 6, see: https://www.qt.io/blog/qt-online-installer-4.0-pre-alpha-released and https://wiki.qt.io/Qt_Contributors_Summit_2019_Program#Qt_Marketplace Intention is that including source components becomes convenient. This could also allow mak

Re: [Development] QtWebEngine and Qt 6 (was: Re: Can your module be included in Qt 6?)

Hi, The situation with Qt WebEngine open-source releases during the commercial-only LTS phase is slightly unclear still as it has a very large 3rd party item it depends on. In essence Qt WebEngine is just bindings of the Chromium HTML5 engine to Qt. Intention is to clarify this before Qt 6.0 i

Re: [Development] Requesting a repository for Qt Quick Calendar

Hi, Open-source license freely available from the repo will be GPLv3, but we will also provide it under the marketplace license with a very decent price tag (allowing to use it with LGPLv3 licensed Qt). Yours, Tuukka On 17.6.2020, 19.59, "Development on behalf of Vincas Dargis" wr

Re: [Development] Switch the main "Qt Build System"

Hi, "Putting that aside, how long should we wait then? " is exactly the question we would like to find the answer to __ My own preference is to make the switch to CMake as soon as possible and use effort to improving the CMake port instead of keeping the qmake as a parallel build system for Q

Re: [Development] Qt Multimedia as Add-on in Qt 6

Hi, There are many add-ons that work perfectly well on mobile. Essentials should be such that are as the name suggest essential for the Qt based applications (or devices). Furthermore, the essentials need to work on all platforms. This means also the embedded and RTOS platforms, not only deskt

Re: [Development] Finishing the transition to the cherry-pick model

Big thanks to everyone involved. Yours, Tuukka From: Development on behalf of Volker Hilsheimer Date: Monday 18. May 2020 at 14.39 To: Qt Project Development Subject: Re: [Development] Finishing the transition to the cherry-pick model > On 15 May 2020, at 13:58, Volker Hilsh

Re: [Development] [Releasing] Qt 5.15.0 Beta4 released

Hi, I would like encourage everyone to test with the Beta 4 as much as possible, not to wait for RC. After the final downmerge to 5.15.0 only fixes to clear blockers should go in, others go into Qt 5.15.1 patch release. Yours, Tuukka On 20.4.2020, 15.17, "Releasing on behalf of Ja

Re: [Development] Finishing the transition to the cherry-pick model

unnecessary merges needed before getting Qt 5.15.0 released. Yours, Tuukka On 20.4.2020, 10.59, "Shawn Rutledge" wrote: > On 20 Apr 2020, at 07:59, Tuukka Turunen wrote: > > > Hi, > > +1 > > I would als

Re: [Development] Finishing the transition to the cherry-pick model

Hi, +1 I would also close Qt 5.14 branch already now. The other option is that some fixes pushed into Qt 5.14 branch at the time of Qt 5.15 RC1 only land in Qt 5.15.1. Neither of these is problematic to me, assuming that the change that may be landing to 5.14 in the last minute is not a as s

Re: [Development] [Releasing] Meeting minutes from Qt Release Team meeting 31.3.2020

Hi, I would like to take this opportunity to thank our release team as well as all others developing Qt. By nature our community is distributed, but typically the developers of The Qt Company are working from an office. However, for the past weeks we all have been working almost completely f

Re: [Development] [Releasing] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

Great! Hopefully the remaining steps towards alpha go nicely. There are quite a few items not yet listed at: https://wiki.qt.io/New_Features_in_Qt_5.15 The new feature highlight is valuable for users, so please lift a few of the key items for each module into the list. Think what are the mos

Re: [Development] [Releasing] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

Hi, In practice we also do have some slack in the schedule exactly to allow sorting everything out. Unfortunately it is often not long enough, but we have delay in getting the alpha out. I do agree that we should include the features that are ready in time - and I do not think there are many w

Re: [Development] (no subject)

Hi Emily and Jenifer, If you wish be removed from the mailing list, you can unsubscribe via: https://lists.qt-project.org Do not send requests asking to be removed from the list, just unsubscribe following the instructions online. Yours, Tuukka On 31.1.2020, 15.29, "Development on

Re: [Development] Forgot your Qt Account password?

Hi, Someone apparently created a Qt Account for the development@qt-project.org mailing list. Good idea, but we do want the accounts to be individual. Yours, Tuukka From: Development on behalf of Qt Project Development Reply-To: Khuram Ali

Re: [Development] Changes to Qt offering

Hi Alberto, No, that is not the plan. For open-source user all releases are to be similar. New patch releases come until the next feature release is out. For commercial license holders, there will be additional patch releases available for selected Qt versions (Qt 5.15, Qt 6.2, ...) Yours,

Re: [Development] Changes to Qt offering

" will the owners of a commercial license be given access to the branch? " => Yes. Yours, Tuukka On 29.1.2020, 13.21, "Giuseppe D'Angelo via Development" wrote: Hi, Il 29/01/20 11:02, Edward Welbourne ha scritto: > They'll be cherry-picked > from there to a (p

Re: [Development] Changes to Qt offering

Hi Antonio, Like the announcement says: "Starting with Qt 5.15, long term support (LTS) will only be available to commercial customers." There is no plan currently to change ongoing Qt 5.9 LTS or Qt 5.12 LTS support period. Qt 5.12 is currently in Strict phase, next step moving to Very strict

Re: [Development] QtPDF did not change license

Hi, Correct. Qt PDF license has not been changed. Some of the contributors preferred to keep the license as LGPL. When we were checking this, some info did not get through. So while the change to GPL would be completely fine for many, there was still concerns and pushback towards changing th

Re: [Development] Proposal for dev

+1 From: Development on behalf of Hausmann Simon Date: Tuesday 28. January 2020 at 13.54 To: Qt Project Development Subject: [Development] Proposal for dev Hi, We have two things going on in dev right now: (1) Quite many changes are going into qtbase right now that change fundamentals,

Re: [Development] Changes to Qt offering

Hi, I do not know why the link does not work. But I remember that post very well. On hindsight, it was too much of a rush back then to ask everyone to create a Qt account immediately. As I wrote in my earlier reply, situation is different now: * Most users have already Qt account * Ma

Re: [Development] Changes to Qt offering

Hi, Well, quite many things have changed since 2015. One important item is that almost one million users have already voluntarily created (and verified) themselves a Qt account. See the FAQ (linked from the blog post): “Q: Will requiring the Qt Account drive away all Qt users? A: We have had

Re: [Development] Changes to Qt offering

Hi, In essence the LTS patch release is a selection of bug fixes and security fixes (including update of 3rd party libraries). The bug fixes and security fixes will go first to dev and are cherry picked back to release branches. After the change every release of Qt will look like a non-lts rel

Re: [Development] Changes to Qt offering

Hi, The criteria to qualify for the small business / startup is: - Revenue or funding less than 100.000 USD annually - Max 5 employees Yours, Tuukka On 27.1.2020, 16.58, "drwho" wrote: On 2020-01-27 9:34 a.m., Lars Knoll wrote: > The third change is that The Qt Company will

Re: [Development] Changes to Qt offering

Hi Ekke, Currently Qt MQTT is not part of Qt for Device Creator or Application Development product, see: https://www.qt.io/features Huge amount of other libraries are included, but unfortunately MQTT is only available as part of the Qt for Automation. Yours, Tuukka On 27.1.2020,

Re: [Development] Contributing to Qt session at Qt World Summit

f so is it viewable somewhere online, for people that weren't there? P. On 07/11/2019, 07:58, "Development on behalf of Tuukka Turunen" wrote: Hi, Yesterday morning at the Qt World Summit we had a session about contributing to

[Development] Contributing to Qt session at Qt World Summit

Hi, Yesterday morning at the Qt World Summit we had a session about contributing to Qt. I was really happy to see over 80 people joining the session at 8 am before the second day keynotes (and after a great party the previous evening). We actually run out of chairs in the room we had booked fo

Re: [Development] Qt Contributors' Summit 2019 - Registration open!

Hello everyone, We have now close to 80 persons registered to the Qt Contributor's Summit. If you are planning to attend, but have not registered yet, please do so now. Latest by 25th October we need to have the registrations in to take care of all the practicalities without a rush. The progr

[Development] Change in open-source licensing of Qt Wayland Compositor, Qt Application Manager and Qt PDF

be in effect by Qt 5.14 release timeframe and later releases. Yours, Tuukka Turunen The Qt Company ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] INTEGRITY

may even want to move items from the wiki to docs. It is fine to have wiki to support, but there is high risk of wiki content to become outdated. Yours, Tuukka On 20/09/2019, 12.03, "Development on behalf of Giuseppe D'Angelo via Development" wrote: Il 20/09/1

Re: [Development] INTEGRITY

Or remove the wiki entry and make sure platform notes in documentation are in shape? No need for duplicated info on these basic items. Yours, Tuukka On 19/09/2019, 23.52, "Development on behalf of Kai Pastor, DG0YT" wrote: Am 19.09.19 um 10:41 schrieb Mutz, Marc via Developm

Re: [Development] INTEGRITY

Hi Marc, A lot of the Qt functionality works perfectly well on INTEGRITY. Even the advanced graphics such as Qt Quick, Qt 3D and Qt 3D Studio. I do not see it reasonable to claim that it is "so far behind all the other supported platforms, as well as its own claim of conformance, that the ques

Re: [Development] Closing 5.13 branch after Qt 5.13.2 release?

open even until Qt 5.14.0 is released, but only receive cherry picked changes from 5.14 branch. Yours, Tuukka On 05/09/2019, 19.30, "Development on behalf of Thiago Macieira" wrote: On Thursday, 5 September 2019 08:51:40 PDT Tuukka Turunen wrote: > That is p

Re: [Development] Closing 5.13 branch after Qt 5.13.2 release?

Lähettäjä: Development käyttäjän Thiago Macieira puolesta Lähetetty: torstaina, syyskuuta 5, 2019 6:25 ip. Vastaanottaja: development@qt-project.org Aihe: Re: [Development] Closing 5.13 branch after Qt 5.13.2 release? On Thursday, 5 September 2019 01:45:16 PDT Tuukka Turunen wrote

Re: [Development] Save the date: Qt Contributors Summit 2019 is 19th - 21st November in Berlin

ty:* Saturday, July 6, 2019 3:21:23 AM > *Vastaanottaja:* development@qt-project.org > *Aihe:* Re: [Development] Save the date: Qt Contributors Summit 2019 is > 19th - 21st November in Berlin > On Friday, 5 July 2019 09:13:52 -03 Tuukka Turunen wrote: &g

  1   2   3   >