[Development] Documenting 3rd party license code (with SPDX?)

tl;dr: Does anyone have experience with SPDX? Qt modules contain quite some 3rd party code under various (permissible) licenses. We've been listening these in the documentation, but this is certainly improvable - while the list is (hopefully) comprehensive, it gives users little help in where

Re: [Development] QtWebkit to vcxproj

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of raven-worx Software > Sent: Wednesday, May 25, 2016 4:11 PM > To: development@qt-project.org > Subject: [Development] QtWebkit to vcxproj > > Hi, > > i am trying to

Re: [Development] Building Always on same path?

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Reynaldo San Juan > Sent: Thursday, June 16, 2016 3:13 PM > To: development@qt-project.org > Subject: [Development] Building Always on same path? > > Hi > I'm developing

Re: [Development] New Qt 5.7.0 RC snapshot available

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Ralf Nolden > [...] > I suggest having a look at https://bugreports.qt.io/browse/QTBUG-49883 > and do some consideration how to handle those issues. If modules are >

Re: [Development] Should the system proxies default setting be switched to true?

+1 for switching to using the system proxy settings by default. I'm still a bit wary about the 'Windows issue' though. To cite our documentation [1]: "On Windows platforms, this function may take several seconds to execute depending on the configuration of the user's system." Was that the

Re: [Development] Does Qt 5.6 still depend on ICU?

> -Ursprüngliche Nachricht- > Von: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] Im Auftrag von Alexander Nassian > Gesendet: Sonntag, 8. Mai 2016 00:56 > An: Roland Winklmeier > Cc: development@qt-project.org > Betreff: Re:

Re: [Development] Remember to rebuild qmake in dev

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Thiago Macieira > Sent: Thursday, July 21, 2016 10:51 PM > To: development@qt-project.org > Subject: Re: [Development] Remember to rebuild qmake in dev > > On

Re: [Development] QtCon rooms for QCS

I've submitted 4 'workshop' sessions, mostly as placeholders. I wouldn't mind replacing them with more urgent / interesting topics though, if there are ones. C++11 library usage would definitely be one I'm interested in myself :) Also, the agenda overview should clearly distinguish between

Re: [Development] [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming...

Hi, Unfortunately, we're having great difficulties to get patches integrated into Qt WebEngine in the last days, right now due to qtlocation not compiling (QTBUG-55229). Unless the situation resolves itself over the weekend, I'd like to ask for an exception for getting features into 5.8 for Qt

Re: [Development] [FYI] commit/review policy refactored

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Wednesday, July 13, 2016 11:08 AM > To: development@qt-project.org; qt-crea...@qt-project.org > Subject: [Development] [FYI] commit/review

Re: [Development] [QtMultimedia] Still is supported, active?

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > [...] > So while I agree that angriness is not helpful for mail list ... messages > like this > are probably the seed to rethink strategy of working with bugs. Somewhat a side remark, but the

Re: [Development] Documenting 3rd party code Qt

t; > On quarta-feira, 20 de julho de 2016 11:13:39 PDT Kai Koehne wrote: > > I had a look at SPDX, README.Chromium, debian/copyright (btw thanks > > for the pointer!). In the end I went for a custom format, because they > > all seem to not quite fit for our use case. Anyh

[Development] Documenting 3rd party code Qt

Hi, A while ago I proposed to generate 3rd party code attributions out of files that are right beside the code, instead of hand-editing 3rdparty.html in qtdoc. I've now a set of patches that are IMO worth to take a look at (also because FF for 5.8 is coming ;) # Information Flow Every 3rd

Re: [Development] Documenting 3rd party code Qt

3rd party code Qt > > On miércoles, 20 de julio de 2016 11:13:39 A. M. ART Kai Koehne wrote: > > Hi, > [snip] > > # File Format > > > > I had a look at SPDX, README.Chromium, debian/copyright (btw thanks > > for the pointer!). > > My pleasure :) >

Re: [Development] Documenting 3rd party code Qt

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > [...] > > That might be helpful, although the current format lacks, for > > example, per- entity copyright (yes, each contributor name). > [...] > I'm genuinely curious though why

Re: [Development] [Qt-creator] [FYI] commit/review policy refactored

> -Original Message- > From: Qt-creator [mailto:qt-creator-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Wednesday, July 13, 2016 12:49 PM > To: development@qt-project.org; qt-crea...@qt-project.org > Subject: Re: [Qt-creator] [Development] [FYI]

Re: [Development] Source break policy for function overloads

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > [...] > We do not have SC promise only BC. We tend to not break SC without > reason, for example we avoid juggling with header files just to "cleanup" > stuff, but definitely we reserve right to

Re: [Development] Change file process & improvement proposal

Looks like this discussion got stuck before reaching a conclusion ... > -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Thursday, November 10, 2016 3:23 PM > To: development@qt-project.org;

Re: [Development] [Releasing] Change file process & improvement proposal

> -Original Message- > From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Thursday, January 26, 2017 12:52 PM > To: development@qt-project.org; releas...@qt-project.org > Subject: Re: [Releasing] [Development] Change file

Re: [Development] [Releasing] Change file process & improvement proposal

> -Original Message- > > [...] > > I therefore suggest to implement Jani's suggestions for the time > > being. If we find out they're not effective, we can always come back > > and look into alternative processes. > > > > 1. Enable [ChangeLog] tag in commit template > > > >

Re: [Development] [Releasing] Change file process & improvement proposal

pencer [mailto:spencer.schum...@echostar.com] > Sent: Thursday, January 26, 2017 5:11 PM > To: Kai Koehne <kai.koe...@qt.io>; Oswald Buddenhagen > <oswald.buddenha...@qt.io>; development@qt-project.org; > releas...@qt-project.org > Subject: Re: [Releasing] [De

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

> -Original Message- > [...] > > This also implies that bug fixes should now get pushed to the 5.9 > > branch and we should close the 5.8 branch soon. > > I disagree. Even if you cannot produce releases from 5.8 anymore, that's our > stable branch. 5.9 isn't stable, yet. If you release

[Development] Using semicolons in JS (QML)

Hi, It’s Friday, so time for some bikeshedding ;) As you might know, the semicolon as a statement separator in JavaScript is optional. That is, most of the time you can just separate commands by newlines. There are a few pathological cases [1] though where a semicolon is needed. It seems the

Re: [Development] [closed] Using semicolons in JS (QML)

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of André Somers > Sent: Thursday, October 06, 2016 11:11 AM > To: development@qt-project.org > Subject: Re: [Development] [closed] Using semicolons in JS (QML) > > So, now we

[Development] [closed] Using semicolons in JS (QML)

Hi, Alright, to close this thread: It seems the majority agrees that using semicolons after JS statement inside a Javascript {} block is a good idea. The suggestion is to follow this in new code. Personally, I will point out missing ; as defects in reviews. Regards Kai > -Original

Re: [Development] Managing branches of Qt's git modules

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Sean Harmer > Sent: Friday, September 30, 2016 12:39 PM > To: development@qt-project.org > Subject: [Development] Managing branches of Qt's git modules > > Hi, > >

Re: [Development] Using semicolons in JS (QML)

om: Development <development-bounces+kai.koehne=qt...@qt-project.org> on behalf of Shawn Rutledge <shawn.rutle...@qt.io> Sent: Friday, September 30, 2016 5:43:57 PM To: development@qt-project.org Subject: Re: [Development] Using semicolons in JS (QML) On 30 Sep 2016, at 14:19,

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Hi, I'd like to request a QUIP number for the handling of 3rd party code in Qt repositories. Anyhow, it seems to me that we're stuck currently in the bootstrapping process of QUIPs: http://quips-qt-io.herokuapp.com/quip-0003.html >The minimum QUIP boostrapping process was discussed: > >1.

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

ions will be > the same as to www/. No idea what qtqt/ should stand for :) > > Kai Koehne wrote: > > > I'd slightly prefer > > > > > > qt/quips > > > > > > because it's not directly related to the website, even if we'll > > > generate a

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Tuesday, November 08, 2016 11:15 AM > To: development@qt-project.org > Subject: Re: [Development] QCS2016 Session Notes - QUIPs for Qt > > On

Re: [Development] Problems compiling QtWebEngine in 5.8.0 beta

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Egor Pugin > Sent: Wednesday, November 09, 2016 10:55 PM > To: Harald Vistnes > Cc: development@qt-project.org > Subject: Re: [Development]

Re: [Development] OpenGL Issues in Qt5.7

> -Original Message- > From: Liu, Jeff (SRDC SW) [mailto:jeff1@amd.com] > Sent: Wednesday, October 26, 2016 7:09 AM > To: gunnar.sle...@jollamobile.com; gun...@sletta.org; Liang Qi > <liang...@qt.io>; Kai Koehne <kai.koe...@qt.io>; development@qt- > pro

Re: [Development] Proposal: Use -qt-zlib configuration in official MinGW builds

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Konrad Rosenbaum > Sent: Tuesday, November 29, 2016 11:03 AM > To: development@qt-project.org > Subject: Re: [Development] Proposal: Use -qt-zlib configuration in official

Re: [Development] Proposal: Use -qt-zlib configuration in official MinGW builds

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Konstantin Tokarev > Sent: Monday, November 28, 2016 3:11 PM > To: development@qt-project.org > Subject: [Development] Proposal: Use -qt-zlib configuration in official >

Re: [Development] qtwebkit

Have you tried running qmake && jom (or nmake) manually inside the qtwebkit source directory? Kai > -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Harald Vistnes > Sent: Friday, December 16, 2016 9:55 AM > To:

Re: [Development] qtwebkit

> -Original Message- > From: Harald Vistnes [mailto:harald.vist...@gmail.com] > Sent: Friday, December 16, 2016 10:01 AM > To: Kai Koehne <kai.koe...@qt.io> > Cc: development@qt-project.org > Subject: Re: [Development] qtwebkit > > Yes, nothing happens. S

[Development] Rules for Third-Party components in Qt 4.8 onwards

Hi, I'd like to put down the rules on how we handle code in Qt that we as Qt contributors do not have copyright over ourselves in a QUIP: https://codereview.qt-project.org/#/c/177201/6/quip-0004.txt I suggest that - Every third party component must be documented by a qt_attribution.json file -

Re: [Development] Rules for Third-Party components in Qt 5.8 onwards

Hi, (I'll try to answer some comments made in the gerrit review here. IMO gerrit works great for editorial stuff, but not for more substantial things). > [Tobias Hunger] > I would make the homepage mandatory in the attribution file. That information > is critical IMHO when you want to find out

Re: [Development] Qt 5.9

> Then let's not drop the 32-bit mingw. But we should add the 64-bit one, and if > possible to 5.8 too. The deal is that we don't want to increase the number of packages in total. Personally, I don't see the qualms with switching to 64 bit for MinGW instantly. For MinGW, there are hardly

[Development] QUIP-7: qt_attribution.json File Format

Hi, This is a heads-up that I've moved parts of QUIP-4 (Third-Party Components in Qt) a while ago into a separate Implementation QUIP. The details about the qt_attribution.json file format are now described in proposed QUIP-7: https://codereview.qt-project.org/#/c/147271/ Comments welcome,

Re: [Development] QUIP-7: qt_attribution.json File Format

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Kai Koehne > Sent: Friday, March 24, 2017 12:25 PM > To: development@qt-project.org > Subject: [Development] QUIP-7: qt_attribution.json F

Re: [Development] Who's responsible for 3rdparty these days (QTBUG-59586)?

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Thiago Macieira > Sent: Sunday, March 19, 2017 8:01 PM > To: development@qt-project.org > Subject: [Development] Who's responsible for 3rdparty these days (QTBUG- > 59586)?

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Marc Mutz > Sent: Tuesday, April 11, 2017 2:25 PM > To: development@qt-project.org > Subject: Re: [Development] Focusing bug fixes to 5.9 branch and patch > releases

Re: [Development] syncqt.pl in C++

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Richard Moore > Sent: Tuesday, March 07, 2017 10:44 PM > To: Lars Knoll > Cc: Thiago Macieira ; Qt development mailing > list

Re: [Development] QT 5.9. Issues with QWebEngine

Hi Sudhir, This is best discussed on bugreports.qt.io, in a bug report for component "WebEngine" in project "Qt". Please include on how you want to set a (non-local) proxy: - through the system settings or - through QNetworkProxy::applicationProxy Regards Kai > -Original Message- >

[Development] Give reviewers ample time to respond

stage immediately if there are other reviewers who haven't given feedback yet. Regards Kai -- Kai Koehne, Senior Manager R | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin

[Development] Please add [ChangeLog] entries to your commits!

Hi, I just noticed that, out of the 61 commits in qtbase/5.9 that are not part of 5.9.0, only one has a [ChangeLog] entry. Some of the commits are either changes to doc, or autotests, but for the rest: If it is not important enough to be mentioned to the user, why is the change in 5.9?

Re: [Development] Please add [ChangeLog] entries to your commits!

> -Original Message- > From: Mitch Curtis > Sent: Monday, May 29, 2017 3:27 PM > To: Kai Koehne <kai.koe...@qt.io>; development@qt-project.org > Subject: RE: Please add [ChangeLog] entries to your commits! > > > [...] > > Please be reminded that a

Re: [Development] Qt Coding style and C++11

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Gatis Paeglis > Sent: Monday, September 18, 2017 12:43 PM > To: André Hartmann ; development@qt-project.org > Subject: Re: [Development] Qt Coding style

Re: [Development] Future of QBS

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > Subject: Re: [Development] Future of QBS > > Hi Jake, > > to use your version control picture: Are we trying to sell subversion by > showing how great that is compared to CVS and RCS, while git is

Re: [Development] Speeding up the review process (was: PostgreSQL cross compile for Pi)

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Martin Smith > [...] > I am a member of the Qt documentation team, and I am often included as a > reviewer for code changes that also include changes to qdoc comments. I >

Re: [Development] Repository Request: qt/licensing

> -Original Message- > [ ..] > Would it perhaps be possible for configure to just look in "well known" > locations in the system where the online installer can place them (or place a > file > that contains the path to licheck) ? That's a good idea, though the online installer has always

Re: [Development] Repository Request: qt/licensing

> -Original Message- > [...] > Can .pro files test for commercial vs. oss licenses? If so, and you create a > non- > Qt project repo, couldn't some .pro in qtbase retrieve licheck, like QtCreator > does here: http://code.qt.io/cgit/qt-creator/qt- > creator.git/tree/qtcreator.pro#n123? >

[Development] Repository Request: qt/licensing

commercial source packages. The goal is to allow proper commercial builds from git, see also https://bugreports.qt.io/browse/QTBUG-5. As such, the repository should be readable by everyone, but write access should be limited to The Qt Company. Kai -- Kai Koehne, Senior Manager R | The Qt Compa

Re: [Development] Repository Request: qt/licensing

te a repository relative to qtbase. Kai From: Stottlemyer, Brett (B.S.) <bstot...@ford.com> Sent: Friday, May 18, 2018 4:45:20 PM To: Kai Koehne; development@qt-project.org Subject: Re: [Development] Repository Request: qt/licensing On 5/18/18, 10:36 AM, "

Re: [Development] Repository Request: qt/licensing

> From: Development on > behalf of Thiago Macieira > > Is the source code for licheck going to be added to the repository? No, I'd only add the binaries. > If not, then the binary cannot be added to the a Qt

[Development] Changing maintainership for Qt Creator modules

eplacement. Project Management & Targets / QML I propose Thomas Hartmann <thomas.hartm...@qt.io> as replacement. Regards Kai -- Kai Koehne, Senior Manager R | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mik

Re: [Development] Did we have to remove cmake's qt5_use_modules?

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > [...] > The Qt promise is to maintain not only source code, but upward binary > compatibility until a major version. > > When said promise is broken immediately after a major version release, as it

Re: [Development] Using Native web view on OS X

> Am I correct in understanding that you are saying that prebuilt Qt packages > cannot be used to submit to the app store, > And that anyone who wishes to use Qt to develop an app on OSX and submit to > the app store must be savvy enough to > Build from source, and locate this thread in the dev

Re: [Development] Symbol clashes with static Qt libraries

Alright, so it seems we have to prefix the symbols we can't hide by static or anonymous namespaces ... For logging categories, I'd like to start using 'qlc' as prefix. See also change https://codereview.qt-project.org/#/c/235631/ for qtbase. Ossi pointed out in the review that, because it is a

[Development] Symbol clashes with static Qt libraries

. This would probably require some major hackery in the build system. No idea whether this is supported also on other platforms, and how hard it would be to pull it off. I'm not volunteering  I guess I'm not the first one who looks into this, so I'm happy to hear advice/opinions  Kai -- Kai Koehne

Re: [Development] Qt Linguist should tell how many strings are in a file

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > [...] > The closest I got was using some web service that we were able to export from > (https://lokalise.co/ ?). Also having a built-in google translate button > would be > very helpful for the

Re: [Development] Qt Linguist should tell how many strings are in a file

> -Original Message- > [...] > It was unfortunately a combination of lokalise.co and my scripts. The > owner/opertator/developer of lokalise was very helpful in adjusting his > service > which apparently supported Qt 3 to Qt4's format. He complained about issues > with the XML, which I

[Development] QML API Review

it's just easier to have this as separate diffs. Regards Kai PS: I intend to codify this http://quips-qt-io.herokuapp.com/quip-0010-API-review.html , but first wanted to establish a consensus. -- Kai Koehne, Senior Manager R | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489

Re: [Development] QtCS 2018: Third-party and security policy

Hi, I've been creating https://codereview.qt-project.org/#/c/233962/2 to pin down what I assume is consensus so far. This is an update to QUIP-4 (https://quips-qt-io.herokuapp.com/quip-0004.html), which regulates how we handle Third-Party Components in Qt. I also added a paragraph that all

Re: [Development] API breackage in Qt3D

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > Subject: Re: [Development] API breackage in Qt3D > > El 1 mar. 2018 6:11 a.m., "Sean Harmer" > escribió: > > > Animation and Extras

[Development] Maintainers: Make sure QML import in documentation and plugins.qmltypes are up to date for 5.11

the build folder where the plugins.qmltypes file belongs to. This is btw also a good way to do an API review. In particular, to check whether all new properties, signals ... have a proper REVISION / are properly versioned. Regards Kai -- Kai Koehne, Senior Manager R | The Qt Company The Qt Co

Re: [Development] Qt API review process (was: Re: Qt 5.11 Alpha released)

(comment below) > -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Jani Heikkinen > Subject: [Development] Qt API review process (was: Re: Qt 5.11 Alpha > released) > > Hi all, > > We have API review ongoing for Qt 5.11.

Re: [Development] Qt 5.12 beta2 released

> -Original Message- > From: Development project.org> On Behalf Of Mark De Wit > Sent: Wednesday, October 17, 2018 9:10 AM > To: development@qt-project.org > Subject: Re: [Development] Qt 5.12 beta2 released > > What is the criteria for blocker? It would be great if WebEngine were

[Development] Dropping remaining support of qtquick1

, in 5.13, or wait for Qt 6. I'd prefer 5.12 if nobody objects  Regards Kai -- Kai Koehne, Senior Manager R | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht

Re: [Development] Qt6: Adding UTF-8 storage support to QString

> -Original Message- > From: Development On Behalf Of Tor > Arne Vestbø > Sent: Friday, January 18, 2019 4:27 PM > To: Jedrzej Nowacki > Cc: Thiago Macieira ; development@qt- > project.org > Subject: Re: [Development] Qt6: Adding UTF-8 storage support to QString > > Picking up on this:

Re: [Development] gnuwin32 in qt5.git

> -Original Message- > From: Development On Behalf Of > [...] > Would it make sense to use a package manager like Conan to provide third > party dependencies as well as Qt modules in source and prebuilt binary form? > That could solve the availability issue and would probably simplify the

Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started

> -Original Message- > From: Development On Behalf Of ekke > Sent: Wednesday, January 23, 2019 9:45 AM > To: development@qt-project.org > Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started > > seems this time it's a rocky path to release Qt 5.12.1 We're still

Re: [Development] CMake && QtCreator cross-compilation for ARM fails

> -Original Message- > [...] > > > The Qt Company has been looking for "employees" to work on Qbs for > > > month before dropping it, apparently nobody responded, or something... > > > > Then that would pretty much explain why they cannot maintain it in the > > long run. > > You are

Re: [Development] automated bulk change closing old issues in the "Need more info" state

> -Original Message- > From: Development project.org> On Behalf Of Uwe Rathmann > Sent: Monday, November 19, 2018 4:10 PM > To: development@qt-project.org > Subject: [Development] automated bulk change closing old issues in the "Need > more info" state > > Hi all, > > I just received 2

[Development] Changes to maintainership of the Qt build system (including qmake)

e for issues in these component. If you feel you can help out in these areas too, please reach out to us! Regards Kai PS: We've also a vacant position in this area: https://www.qt.io/open-positions/software-engineer-tooling-1543483062 -- Kai Koehne, Senior Manager R | The Qt Company The Qt Co

Re: [Development] Qt 5.12 and debug/warnings messages

> -Original Message- > [...] > So I've supposed the Qt 5.12.0 release (MSVC2017 / 32bit) have been build > with QT_NO_WARNING_OUTPUT and QT_NO_DEBUG_OUTPUT. That's not the case, at least for the official packages. QT_NO_WARNING_OUTPUT, QT_NO_DEBUG_OUTPUT anyway does only affect the code

Re: [Development] Good idea to update Windows 10 to 1809 - Redstone 5?

> -Original Message- > From: Development On Behalf Of > Tony Sarajärvi > Sent: Thursday, January 17, 2019 2:23 PM > To: development@qt-project.org > Subject: [Development] Good idea to update Windows 10 to 1809 - Redstone > 5? > > Hi > > We have this thing that we like to try to update

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

Somewhat related: I suggest to stop listening all changes in the commit message template. See e.g. https://codereview.qt-project.org/#/c/253950/ This makes the commit message unnecessarily long, and also means that, if you grep though git log history for a specific change, you hit the

Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started

> -Original Message- > From: Development On Behalf Of > Mark De Wit > Sent: Wednesday, January 30, 2019 11:13 AM > To: development@qt-project.org > Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started > > Selecting MSVC 2015 64-bit + Qt WebEngine for 5.12.1 in

Re: [Development] QUIP-13 for Qt Examples and Demos

commits. Regards Kai > -Original Message- > From: Development On Behalf Of > Kai Koehne > Sent: Thursday, November 22, 2018 11:26 AM > To: development@qt-project.org > Subject: [Development] QUIP-13 for Qt Examples and Demos > > Hi, > > I'd like to propose