From jani.heikkinen at qt.io Fri Jun 2 08:29:17 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Fri, 2 Jun 2017 06:29:17 +0000 Subject: [Releasing] Qt 5.10 Feature Freeze is coming Message-ID: Hi all! Just a kindly reminder: Qt 5.10 Feature Freeze date is 8.8.2017 so there isn't really more than 2 months time left to get new features in (see https://wiki.qt.io/Qt_5.10_Release ). We kept final schedule with Qt 5.9.0 and we need to continue that with Qt 5.10. So if you already now see that some feature won't be ready early enough please postpone it to 5.11 instead. Please make sure all new features are visible in new feature page (https://wiki.qt.io/New_Features_in_Qt_5.10) as soon as possible. Please also make sure new features are fulfilling ff criteria (https://wiki.qt.io/Qt_5_Feature_Freeze). And make sure all new modules are in qt5.git early enough, at this time latest at the end of June (also possible new Technology Preview ones): FF is immediately after summer holiday period and we need to create configurations etc for those as well before FF. That's why we need to get new modules in qt5.git as early as possible. At the moment I don't know any new module for Qt 5.10. If there will be some please inform me immediately with details(we can start preparations for those already now): - Module name & repository - Officially supported/TP - Description for installer - Supported platforms - etc And also inform me if some already existing module change it's state (e.g TP->officially supported, deprecated etc) br, Jani Heikkinen Release Manager From tuukka.turunen at qt.io Fri Jun 2 09:04:02 2017 From: tuukka.turunen at qt.io (Tuukka Turunen) Date: Fri, 2 Jun 2017 07:04:02 +0000 Subject: [Releasing] [Development] Qt 5.10 Feature Freeze is coming In-Reply-To: References: Message-ID: Hi, If you are still developing in a feature branch, please merge to dev as soon as possible. Unless you are already aiming to Qt 5.11, that is. We should avoid "last minute" merges as these are likely to cause problems. Yours, Tuukka ________________________________ From: Development on behalf of Jani Heikkinen Sent: Friday, June 2, 2017 9:29:17 AM To: development at qt-project.org Cc: releasing at qt-project.org Subject: [Development] Qt 5.10 Feature Freeze is coming Hi all! Just a kindly reminder: Qt 5.10 Feature Freeze date is 8.8.2017 so there isn't really more than 2 months time left to get new features in (see https://wiki.qt.io/Qt_5.10_Release ). We kept final schedule with Qt 5.9.0 and we need to continue that with Qt 5.10. So if you already now see that some feature won't be ready early enough please postpone it to 5.11 instead. Please make sure all new features are visible in new feature page (https://wiki.qt.io/New_Features_in_Qt_5.10) as soon as possible. Please also make sure new features are fulfilling ff criteria (https://wiki.qt.io/Qt_5_Feature_Freeze). And make sure all new modules are in qt5.git early enough, at this time latest at the end of June (also possible new Technology Preview ones): FF is immediately after summer holiday period and we need to create configurations etc for those as well before FF. That's why we need to get new modules in qt5.git as early as possible. At the moment I don't know any new module for Qt 5.10. If there will be some please inform me immediately with details(we can start preparations for those already now): - Module name & repository - Officially supported/TP - Description for installer - Supported platforms - etc And also inform me if some already existing module change it's state (e.g TP->officially supported, deprecated etc) br, Jani Heikkinen Release Manager _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Wed Jun 7 08:57:10 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 7 Jun 2017 06:57:10 +0000 Subject: [Releasing] Qt 5.10 pre-built bunaries Message-ID: Hi all, There has been discussion ongoing about 5.10 supported platforms and CI configurations. What we haven't agreed yet is Qt 5.10 pre-built binaries. I don't see big need to change anything from 5.9 but there is still couple of things on my mind: - Should we now switch from MinGW32 bit -> MinGW 64bit ones? With 5.9 this was too early but would it be time to do it now? Offering both isn't an option. And 5,9 is LTS so 5.10 could be good release to change that... - Can we start using RHEL 7.4 for linux packaging? Tony is planning to add RHEL 7.4 in CI and so on it would be wise to replace 7.2 with 7.4 in the packaging as well Is there some other change proposals which we should discuss about? br, Jani From lars.knoll at qt.io Wed Jun 7 09:30:15 2017 From: lars.knoll at qt.io (Lars Knoll) Date: Wed, 7 Jun 2017 07:30:15 +0000 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: References: Message-ID: Hi Jani, > On 7 Jun 2017, at 08:57, Jani Heikkinen wrote: > > Hi all, > > There has been discussion ongoing about 5.10 supported platforms and CI configurations. What we haven't agreed yet is Qt 5.10 pre-built binaries. I don't see big need to change anything from 5.9 but there is still couple of things on my mind: > > - Should we now switch from MinGW32 bit -> MinGW 64bit ones? With 5.9 this was too early but would it be time to do it now? Offering both isn't an option. And 5,9 is LTS so 5.10 could be good release to change that... We got a lot of questions about 32bit binaries still in the comments to the release blog. But those were pretty much all about VS2017. I'd personally be happy to move more towards 64 bit, but we should somehow find out how much 32bit is still required by our users. > > - Can we start using RHEL 7.4 for linux packaging? Tony is planning to add RHEL 7.4 in CI and so on it would be wise to replace 7.2 with 7.4 in the packaging as well Sounds good to me, unless anybody knows about any reasons why we should stay on 7.2. > > Is there some other change proposals which we should discuss about? I think we should strongly consider dropping 32bit for iOS. Cheers, Lars From Jake.Petroules at qt.io Wed Jun 7 17:46:55 2017 From: Jake.Petroules at qt.io (Jake Petroules) Date: Wed, 7 Jun 2017 15:46:55 +0000 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: References: Message-ID: <9FB9EF89-CBF4-4F3A-91C1-5C66B31AA52D@qt.io> > On Jun 7, 2017, at 12:30 AM, Lars Knoll wrote: > > Hi Jani, > >> On 7 Jun 2017, at 08:57, Jani Heikkinen wrote: >> >> Hi all, >> >> There has been discussion ongoing about 5.10 supported platforms and CI configurations. What we haven't agreed yet is Qt 5.10 pre-built binaries. I don't see big need to change anything from 5.9 but there is still couple of things on my mind: >> >> - Should we now switch from MinGW32 bit -> MinGW 64bit ones? With 5.9 this was too early but would it be time to do it now? Offering both isn't an option. And 5,9 is LTS so 5.10 could be good release to change that... > > We got a lot of questions about 32bit binaries still in the comments to the release blog. But those were pretty much all about VS2017. I'd personally be happy to move more towards 64 bit, but we should somehow find out how much 32bit is still required by our users. >> >> - Can we start using RHEL 7.4 for linux packaging? Tony is planning to add RHEL 7.4 in CI and so on it would be wise to replace 7.2 with 7.4 in the packaging as well > > Sounds good to me, unless anybody knows about any reasons why we should stay on 7.2. >> >> Is there some other change proposals which we should discuss about? > > I think we should strongly consider dropping 32bit for iOS. I thought we already agreed to do this. :) With Apple announcing that iOS 11 will no longer support 32-bit applications, let alone CPUs, there's very little value in us supporting it. 80-90% of iOS devices will likely be on iOS 11 in the first week or month of its release, and of the percentage that aren't, only a minority will be the 32-bit iPhone 5. We probably even support too many iOS versions as it is. Apple's official recommendation is that your deployment target should be "major version one below current, maximum minor version" - i.e. when iOS 11 is out, your deployment target should be 10.3. > Cheers, > Lars > > _______________________________________________ > Development mailing list > Development at qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Jake Petroules - jake.petroules at qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io From thiago.macieira at intel.com Wed Jun 7 22:09:36 2017 From: thiago.macieira at intel.com (Thiago Macieira) Date: Wed, 07 Jun 2017 13:09:36 -0700 Subject: [Releasing] Qt 5.10 pre-built bunaries In-Reply-To: References: Message-ID: <2568778.hfst4LOck6@tjmaciei-mobl1> On Tuesday, 6 June 2017 23:57:10 PDT Jani Heikkinen wrote: > Hi all, > > There has been discussion ongoing about 5.10 supported platforms and CI > configurations. What we haven't agreed yet is Qt 5.10 pre-built binaries. I > don't see big need to change anything from 5.9 but there is still couple of > things on my mind: > > - Should we now switch from MinGW32 bit -> MinGW 64bit ones? With 5.9 this > was too early but would it be time to do it now? Offering both isn't an > option. And 5,9 is LTS so 5.10 could be good release to change that... > > - Can we start using RHEL 7.4 for linux packaging? Tony is planning to add > RHEL 7.4 in CI and so on it would be wise to replace 7.2 with 7.4 in the > packaging as well > > Is there some other change proposals which we should discuss about? I'd like to propose raising the minimum version for GCC to 4.8.1, which is the first C++11 complete version, or higher. The reason for this is actually to drop GCC 4.7 and earlier, which have a few bugs with their C++11 support. GCC 4.7 has been the minimum since Qt 5.7.0 and is now 5 years old. I've just been bitten by one with QRandomGenerator, relating to calling static member functions from a lambda. The workaround suggested in the Coding Convention is not applicable going forward because Clang 5.0 will produce a warning about it (I've updated the wiki), so we have to choose which one we'll support very shortly, as soon as Apple begins shipping Clang based on the current trunk version in XCode. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center From thiago.macieira at intel.com Thu Jun 8 00:10:57 2017 From: thiago.macieira at intel.com (Thiago Macieira) Date: Wed, 07 Jun 2017 15:10:57 -0700 Subject: [Releasing] Dropping older compilers for Qt 5.10 (was: Qt 5.10 pre-built bunaries) In-Reply-To: <4677251496867430@web43g.yandex.ru> References: <2568778.hfst4LOck6@tjmaciei-mobl1> <4677251496867430@web43g.yandex.ru> Message-ID: <4163411.lHBuFDpqgs@tjmaciei-mobl1> On quarta-feira, 7 de junho de 2017 13:30:30 PDT Konstantin Tokarev wrote: > FWIW, the first really C++11 complete version of GCC is 4.9, 4.8 still has a > number of bugs that result in internal compiler errors, compilation errors, > or runtime errors in some non-trivial but valid C++11 code. See for example > patches in [1, 2] 4.9 is a 4-year-old compiler today. I'd love to get rid of the buggy 5.3.x, but that's too recent. Quick survey shows: * GCC 4.9 in Ubuntu 14.04 LTS, Debian Jessie, Fedora 21 [*] * GCC 4.8.5 in the latest OpenSUSE Leap, SUSE Linux Enterprise. and CentOS / RHEL. [*] F21 is not supported by Fedora; minimum support at the time of Qt 5.10's release will be F24 So I'm guessing we should require GCC 4.8.5 (all the latest fixes). This will give us full C++11 support in GCC. Clang claims to be fully C++14 compliant in 3.4, which we already require. Then there's MSVC. So... should we begin thinking of dropping MMSVC 2013? We'll gain by doing that: * default and delete members * alignas & alignof * inheriting constructors * noexcept * range for (without having to check if it really works) * ref qualifiers (no more need for #ifdef) * thread_local (QRandomGenerator benefits from this, also obviates the need to introduce Q_THREAD_LOCAL) * user defined literals * Unicode strings * unrestricted unions Another benefit is that MSVC 2017 and 2015 are supposedly binary compatible with each other. With care, we can even use this feature in Qt. If we require MSVC 2015 with the most recent update (which is over a year old now), in addition we get: * attributes * thread-safe statics (finally! could drop the fallback from Q_GLOBAL_STATIC! oh, wait, Apple...) * uniform initialisation (without having to check if it really works) In other words, there'll be exactly one C++11 feature we won't be able to indiscriminately use: * constexpr (plus whatever fails due to issues in the the Standard Libraries) -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center From lars.knoll at qt.io Thu Jun 8 08:23:51 2017 From: lars.knoll at qt.io (Lars Knoll) Date: Thu, 8 Jun 2017 06:23:51 +0000 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: <2568778.hfst4LOck6@tjmaciei-mobl1> References: <2568778.hfst4LOck6@tjmaciei-mobl1> Message-ID: <17A4B969-B2B7-405E-B746-9D60E404A996@qt.io> On 7 Jun 2017, at 22:09, Thiago Macieira > wrote: On Tuesday, 6 June 2017 23:57:10 PDT Jani Heikkinen wrote: Hi all, There has been discussion ongoing about 5.10 supported platforms and CI configurations. What we haven't agreed yet is Qt 5.10 pre-built binaries. I don't see big need to change anything from 5.9 but there is still couple of things on my mind: - Should we now switch from MinGW32 bit -> MinGW 64bit ones? With 5.9 this was too early but would it be time to do it now? Offering both isn't an option. And 5,9 is LTS so 5.10 could be good release to change that... - Can we start using RHEL 7.4 for linux packaging? Tony is planning to add RHEL 7.4 in CI and so on it would be wise to replace 7.2 with 7.4 in the packaging as well Is there some other change proposals which we should discuss about? I'd like to propose raising the minimum version for GCC to 4.8.1, which is the first C++11 complete version, or higher. The reason for this is actually to drop GCC 4.7 and earlier, which have a few bugs with their C++11 support. GCC 4.7 has been the minimum since Qt 5.7.0 and is now 5 years old. I'm not necessarily against it, as I believe we need to move forward with our compilers. But I am unsure how much sense this makes as long as we're still supporting VC++ 2013. And dropping GCC 4.7 would imply dropping support for QNX 6. Cheers, Lars I've just been bitten by one with QRandomGenerator, relating to calling static member functions from a lambda. The workaround suggested in the Coding Convention is not applicable going forward because Clang 5.0 will produce a warning about it (I've updated the wiki), so we have to choose which one we'll support very shortly, as soon as Apple begins shipping Clang based on the current trunk version in XCode. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars.knoll at qt.io Thu Jun 8 08:45:24 2017 From: lars.knoll at qt.io (Lars Knoll) Date: Thu, 8 Jun 2017 06:45:24 +0000 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: References: <2568778.hfst4LOck6@tjmaciei-mobl1> <17A4B969-B2B7-405E-B746-9D60E404A996@qt.io> Message-ID: <1D9E87ED-8CA5-404B-BBD8-5E18E921B51D@qt.io> > On 8 Jun 2017, at 08:37, Ville Voutilainen wrote: > > On 8 June 2017 at 09:23, Lars Knoll wrote: >>> I'd like to propose raising the minimum version for GCC to 4.8.1, which is >>> the >>> first C++11 complete version, or higher. The reason for this is actually to >>> drop GCC 4.7 and earlier, which have a few bugs with their C++11 support. >>> GCC >>> 4.7 has been the minimum since Qt 5.7.0 and is now 5 years old. >> >> I'm not necessarily against it, as I believe we need to move forward with >> our compilers. But I am unsure how much sense this makes as long as we're >> still supporting VC++ 2013. >> >> And dropping GCC 4.7 would imply dropping support for QNX 6. > > I'll make the observation that we just released an LTS release that > will support QNX 6 > until the next LTS comes out. Sure, it's still important that we all know about the possible side effects of dropping a compiler version before making the decision. IMO, keeping VC++ 2013 while dropping gcc 4.7 doesn't make too much sense. We either keep both or drop both. Cheers, Lars From jani.heikkinen at qt.io Mon Jun 12 13:35:35 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Mon, 12 Jun 2017 11:35:35 +0000 Subject: [Releasing] Qt 5.9.1 soft branching started Message-ID: Hi all, We have today started soft branching from '5.9' to '5.9.1'. That way we should be able to release Qt 5.9.1 still during June. So please use '5.9.1' for new changes targeted to Qt 5.9.1 release. We will do final downmerge from '5.9' to '5.9.1' this Friday (16.6) and after that '5.9' will be for Qt 5.9.2. And please note: We are planning to do regular patch level releases for Qt 5.9 series so no any nice-to-haves in '5.9.1', just fixes for really critical issues. All others must be done in '5.9' & can wait Qt 5.9.2 release. So '5.9.1' is just for getting Qt 5.9.1 quickly out... And at this time we really want to do Qt 5.9.1 on time meaning we won't delay the release because of issues which were already in Qt 5.9.0 release. And we will check case by case all new regressions if those could really delay the release or not: Qt 5.9.2 is planned to be released already on August. br, Jani Heikkinen Release Manager From jani.heikkinen at qt.io Tue Jun 13 12:52:49 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 13 Jun 2017 10:52:49 +0000 Subject: [Releasing] Qt 5.10 pre-built bunaries In-Reply-To: References: Message-ID: Hi, As a conclusion of subject: only change related to pre-built binaries for 5.10 (from Qt 5.9) is dropping 32 bit iOS. And from 5.11 -> we will drop MSVC2013 as well. There isn't conclusion about mingw yet but let's agree to switch from mingw 32 bit to 64 bit one in 5.11 -> There were also discussion about minimum GCC version but it isn't directly related to pre-built binaries and that's why it needs to be concluded in different thread br Jani From jani.heikkinen at qt.io Wed Jun 14 08:00:40 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 14 Jun 2017 06:00:40 +0000 Subject: [Releasing] First Qt 5.9.1 snapshot available In-Reply-To: References: Message-ID: Hi all, We have first Qt 5.9.1 snapshot available via online installer. It is a separate 5.9.1 node, not as an update to Qt 5.9.0. Instructions how to install it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer Content of the snapshot is based on https://codereview.qt-project.org/#/c/196614/, delta to Qt 5.9.0 as an attachment. RTA testing is ongoing and snapshot seems to be pretty much OK. So please test the snapshot & report your effort via https://wiki.qt.io/Qt59_release_testing And please note: We will do regular patch releases for 5.9 series and so on we won't block the release because of old issues. Qt 5.9.1 is released on June and 5.9.2 is targeted to be released on August so if there is still bad issues open in 5.9.1 there is time to fix those for soon coming Qt 5.9.2 (or even Qt 5.9.3 which should be out ~September...) br, Jani -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: qt5.9.1-delta.txt URL: From jani.heikkinen at qt.io Wed Jun 14 08:27:30 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 14 Jun 2017 06:27:30 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 13.06.2017 Message-ID: Meeting minutes from Qt Release Team meeting 13th June 2017 Qt 5.9.1 status: - First snapshot for testing available - Soft branching ongoing, target to finalize branching Fri 16.6.2017 - Target to create Qt 5.9.1 "rc" immediately after branching finished - And target is to release Qt 5.9.1 during week 26 * We will minimize changes in '5.9.0' branch & get in just a must have fixes for possible new issues from "rc" * We won't block patch releases for 5.9 series because of some old issue. If fix isn't in early enough then it will be in next one. ** If we managed to do these regular releases that shouldn't be a problem at all - Release team will do initial change files for the release immediately after branching finalized. * Full git log will be as a base & maintainer can do modifications if needed. Otherwise initial ones will be used Qt 5.10 and Qt 5.6.3 snapshots - qt5.git integrations have gone through pretty well in all branches so it is pretty much just finalizing the installer confs - Target is still to get first ones for testing during June * We are really hurry with all this so we aren't sure if we managed to get both out in time Next meeting 1.8.2017 16:00 CET br, Jani Heikkinen Release Manager irc log below: [17:00:16] akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping [17:00:25] jaheikki3: pong [17:00:56] jaheikki3: pong [17:01:10] jaheikki3: pong [17:01:59] time to start qt release team meeting [17:02:14] On agenda today: [17:02:27] pong [17:02:42] - Qt 5.9.1 status & plan forward [17:03:06] - Qt 5.10 & 5.6.3 snapshot status [17:03:18] Any additional item to the agenda? [17:03:48] you're covering all possible releases, so no :-) [17:05:27] ;) [17:05:37] Ok, lets start from 5.9.1: [17:06:04] First snapshot for testing available internally [17:06:28] It will be publicly available latest tomorrow morning [17:07:03] RTA already ongoing, all seems to be OK so far [17:07:36] Soft branching ongoing, target to finalize branching this Friday [17:08:22] And target is to create "RC" for testing immediately after branching is finalized [17:09:29] -*- thiago finished a Clang 5.0 build of 5.9.1 [17:09:32] patches pushed [17:09:39] And if no new blockers reported from RC put Qt 5.9.1 out at week starting 26th June [17:09:40] only qtnetworkauth had build issues [17:10:10] thiago: ok, so those should be in early enough [17:11:55] And because we are planning to do regular patch releases for 5.9 series we shouldn't block any because of some old issue. If fix isn'yt in early enough then it will be in next one. If we managed to do these releases regularly that shouldn't be a problem at all [17:12:24] clang 5.0 isn't released, so this is not urgent [17:12:52] That's all about 5.9.1. Any comments or questions? [17:13:15] should we ping maintainers for changes files [17:13:47] or commit the templates? [17:13:55] carewolf: yes, good point. We will be quite hurry with those. [17:14:23] just push reviews with the default "no changes.."... [17:14:56] or take put git log in & let maintainer clean it up if needed? [17:15:48] Creating initial ones containg all stuff from git isn't that big issue, would that be ok? [17:15:58] yup [17:16:03] +1 [17:16:35] Great, we will create initial ones immediately when branching is finalized [17:17:25] Ok, that was all about 5.9.1 at this time [17:17:42] Then short update of Qt 5.10 and 5.6.3 snapshots: [17:18:03] - Target is still to get first ones for testing during June [17:18:51] - qt5.git integrations have gone through pretty well in all branches so it is pretty much just finalizing the installer confs [17:19:20] - but we are reall yhurry with all this so we aren't sure if we managed to get both out in time [17:20:11] - we wil ldo our best but if we don't have enough time then we will continue with those immediately after summer hoilidays [17:21:11] the snapshot or 5.6.3? [17:21:28] carewolf: Yes? [17:21:36] which one will we have trouble getting out? [17:21:41] both? [17:22:13] Well, both is still ongoing. And for us priority order is 5.9.1, 5.10 and then 5.6.3 [17:22:24] I mean for 5.6.3, you are talking about also having a snapshot for that? [17:22:32] ok [17:23:35] yes, we will create snapshot for 5.6.3 as soon as possible as well .There is really much changes in '5.6' since 5.6.2 release and so on we need most probably few iterations before we are ready for Qt 5.6.3 release [17:23:49] -*- thiago disagrees, 5.6.3 should come before 5.10 [17:24:13] yes. I also agree 5.6.3 is more important, and it is great it has an RC. [17:24:33] especially in webengine where it upgraded the engine [17:25:53] though snapshot 5.6.3, snapshot 5.10, 5.6.3, snapshot 5.10 continued, would be fine. and we can then see where they land over the vacation [17:25:54] In the bigger picture 5.10 is more important for us. To get first snapshot out makes our life easier with Alpha & rest of schedule as well. [17:26:28] well, that is upside down [17:26:39] yes, but 5.10 is not yet in feature freeze or alpha stage, so it is bit low priority currently [17:26:40] 5.6 is LTS and we haven't released anything in almost a year [17:27:03] how will users trust us to produce LTS when our track record is that we'll go for the shiny new thing instead? [17:28:36] and 5.6.3 was scheduled for early 2017, so it is 6 months late at this point [17:28:45] well, on the other hand you are right. But we will show with 5.9 series the new way of doing reqular releases. 5.6.3 is a bit difficult for us because it is so much different than 5.9 -> [17:29:17] But I don't mean we don't try to get 5.6.3 out as soon as possible [17:29:29] but if we get the snapshot out, people have a chance to test that, and at least we have something, then we can package it when time permits [17:29:54] exactly [17:30:46] So let's see what we can do still before summer holidays [17:31:17] We will do our best and let's hope it is enough to get all that out ;) [17:33:03] I think that's all at this time. I cannot join next Tuesday and then I start my summer holiday. So let's have next meeting Tue 1st August at this same time. OK? [17:35:46] So, no release manager ;-) [17:35:48] ? [17:36:30] fkleint: You mean for 5.9.1? akseli will put the release out ;) [17:36:37] oki [17:37:51] Ok, let's end this meeting now. Thanks for your participation! [17:37:53] Bye [17:37:57] bye From lars.knoll at qt.io Fri Jun 16 08:16:30 2017 From: lars.knoll at qt.io (Lars Knoll) Date: Fri, 16 Jun 2017 06:16:30 +0000 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: References: Message-ID: <1E4EBEB3-FAB8-41D9-A412-8DF46BE027A9@qt.io> > On 16 Jun 2017, at 01:27, Sérgio Martins wrote: > > On Tue, Jun 13, 2017 at 11:52 AM, Jani Heikkinen wrote: >> Hi, >> >> As a conclusion of subject: >> >> only change related to pre-built binaries for 5.10 (from Qt 5.9) is dropping 32 bit iOS. >> And from 5.11 -> we will drop MSVC2013 as well. > > Hi Jani, > > > From what I read in this thread I don't see that conclusion re 2013, > in fact there seems to be more people and arguments in favor of > removing it. We’re one month away from the feature freeze, and in July half of the developers are on vacation. So there’s relatively little benefit from dropping 2013 now, as dev currently works with it. So I’m with Jani here, and think that dropping it from the dev branch in a month from now, when we branch 5.10 makes most sense. Cheers, Lars From thiago.macieira at intel.com Fri Jun 16 08:36:57 2017 From: thiago.macieira at intel.com (Thiago Macieira) Date: Thu, 15 Jun 2017 23:36:57 -0700 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: <1E4EBEB3-FAB8-41D9-A412-8DF46BE027A9@qt.io> References: <1E4EBEB3-FAB8-41D9-A412-8DF46BE027A9@qt.io> Message-ID: <78847837.tdR9O3rfJY@tjmaciei-mobl1> On Thursday, 15 June 2017 23:16:30 PDT Lars Knoll wrote: > We’re one month away from the feature freeze, and in July half of the > developers are on vacation. So there’s relatively little benefit from > dropping 2013 now, as dev currently works with it. The difference is whether we have to put up with MSVC 2013 and find workarounds for half a month or for 7 months. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center From lars.knoll at qt.io Fri Jun 16 08:43:40 2017 From: lars.knoll at qt.io (Lars Knoll) Date: Fri, 16 Jun 2017 06:43:40 +0000 Subject: [Releasing] [Development] Qt 5.10 pre-built bunaries In-Reply-To: <78847837.tdR9O3rfJY@tjmaciei-mobl1> References: <1E4EBEB3-FAB8-41D9-A412-8DF46BE027A9@qt.io> <78847837.tdR9O3rfJY@tjmaciei-mobl1> Message-ID: <8F57244B-110F-4AD7-AA2B-4BCB10C70A32@qt.io> > On 16 Jun 2017, at 08:36, Thiago Macieira wrote: > > On Thursday, 15 June 2017 23:16:30 PDT Lars Knoll wrote: >> We’re one month away from the feature freeze, and in July half of the >> developers are on vacation. So there’s relatively little benefit from >> dropping 2013 now, as dev currently works with it. > > The difference is whether we have to put up with MSVC 2013 and find workarounds > for half a month or for 7 months. I also want to get rid of it rather sooner than later. But we have to deal with the compiler for quite a while in 5.9 anyway, and I’d expect that a lot of the bug fixes will go there. So the question is how much we’re gaining dropping it now a month before the 5.10 freeze. In any case, I’ve asked for download numbers for 2013. I’d like to see those before we make the decision. Cheers, Lars From jani.heikkinen at qt.io Mon Jun 19 08:20:58 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Mon, 19 Jun 2017 06:20:58 +0000 Subject: [Releasing] [Development] First Qt 5.9.1 snapshot available In-Reply-To: References: Message-ID: > -----Original Message----- > From: André Hartmann [mailto:aha_1980 at gmx.de] > Sent: sunnuntai 18. kesäkuuta 2017 18.25 > To: Jani Heikkinen ; development at qt-project.org; > interest at qt-project.org > Cc: releasing at qt-project.org > Subject: Re: [Development] First Qt 5.9.1 snapshot available > > Hi Jani, > > I've got two questions regarding the 5.9.1 release: > > 1. There have been no "changes file" templates provided so far. I guess this > will lead to last-minute hectic if you want to release in June. It would be good > to have such templates as soon as the release branch is created. To be honest, it should be maintainers who does these change files from the begining, not the release team. But because it seems to be really hard to be done we in the release team have done these initial ones lately. Doing these too early won't help at all because many changes might be missing and that's why we are planning to do these immediately after branching from '5.9' -> '5.9.1' is finalized. I know it will be tight but let's try to get it done really quickly at this time. But to be honest we need to find a better way to do this now when we are trying to do these reqular patch level releases... > > 2. For 5.8.0, I saw that binary compatibility files were added. Did I miss > something or is this discontinued for 5.9.0? How do you assure BC during the > 5.9 patch releases? > No, this is continuing. 5.9.0 bc files are still missing and 5.9.1 is still compared to 5.8.0. 5.9.0 bc files will be added as soon as possible br, Jani > Best regards, > André > > Am 14.06.2017 um 08:00 schrieb Jani Heikkinen: > > Hi all, > > > > We have first Qt 5.9.1 snapshot available via online installer. It is > > a separate 5.9.1 node, not as an update to Qt 5.9.0. Instructions how > > to install it here: > > https://wiki.qt.io/How_to_get_snapshot_via_online_installer > > > > Content of the snapshot is based on https://codereview.qt- > project.org/#/c/196614/, delta to Qt 5.9.0 as an attachment. > > > > RTA testing is ongoing and snapshot seems to be pretty much OK. So > > please test the snapshot & report your effort via > > https://wiki.qt.io/Qt59_release_testing > > > > And please note: We will do regular patch releases for 5.9 series and > > so on we won't block the release because of old issues. Qt 5.9.1 is > > released on June and 5.9.2 is targeted to be released on August so if > > there is still bad issues open in 5.9.1 there is time to fix those for > > soon coming Qt 5.9.2 (or even Qt 5.9.3 which should be out > > ~September...) > > > > br, > > Jani > > > > > > > > > > > > _______________________________________________ > > Development mailing list > > Development at qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development > > From jani.heikkinen at qt.io Mon Jun 19 08:31:59 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Mon, 19 Jun 2017 06:31:59 +0000 Subject: [Releasing] Qt 5.9.1 branching finalized In-Reply-To: References: Message-ID: Hi all, Final downmerge is now done and '5.9' is for '5.9.2' from now on. We will start doing Qt 5.9.1 "rc" now to see if there is still some issue to be fixed before official release. But the target is that current '5.9.1' is final content for the release so please not try to get in any nice-to-haves anymore. Change files are still missing and we will do those soon today. Let's get those in as soon as possible br, Jani ________________________________________ From: Development on behalf of Jani Heikkinen Sent: Monday, June 12, 2017 2:35 PM To: development at qt-project.org Cc: releasing at qt-project.org Subject: [Development] Qt 5.9.1 soft branching started Hi all, We have today started soft branching from '5.9' to '5.9.1'. That way we should be able to release Qt 5.9.1 still during June. So please use '5.9.1' for new changes targeted to Qt 5.9.1 release. We will do final downmerge from '5.9' to '5.9.1' this Friday (16.6) and after that '5.9' will be for Qt 5.9.2. And please note: We are planning to do regular patch level releases for Qt 5.9 series so no any nice-to-haves in '5.9.1', just fixes for really critical issues. All others must be done in '5.9' & can wait Qt 5.9.2 release. So '5.9.1' is just for getting Qt 5.9.1 quickly out... And at this time we really want to do Qt 5.9.1 on time meaning we won't delay the release because of issues which were already in Qt 5.9.0 release. And we will check case by case all new regressions if those could really delay the release or not: Qt 5.9.2 is planned to be released already on August. br, Jani Heikkinen Release Manager _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development From julius.bullinger at intel.com Mon Jun 19 15:16:07 2017 From: julius.bullinger at intel.com (Bullinger, Julius) Date: Mon, 19 Jun 2017 13:16:07 +0000 Subject: [Releasing] First Qt 5.9.1 snapshot available In-Reply-To: References: Message-ID: <7FC8D04D3E708B4AA8248F6D64E0CB2136B860CC@IRSMSX104.ger.corp.intel.com> Hi, Since there is only one global Qt Quick Compiler component, it seems like it will be updated to 5.9.1-0-201706131028 even if the snapshot is not installed. Is this intended behavior? Are the Qt Quick Compiler versions compatible between releases? Can I also use it with Qt 5.9.0? What about Qt 5.7.1? If not, is there a way to install an older version? Thanks and br, Julius -----Original Message----- From: Interest [mailto:interest-bounces+julius.bullinger=intel.com at qt-project.org] On Behalf Of Jani Heikkinen Sent: Wednesday, June 14, 2017 08:01 To: development at qt-project.org; interest at qt-project.org Cc: releasing at qt-project.org Subject: [Interest] First Qt 5.9.1 snapshot available Importance: High Hi all, We have first Qt 5.9.1 snapshot available via online installer. It is a separate 5.9.1 node, not as an update to Qt 5.9.0. Instructions how to install it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer Content of the snapshot is based on https://codereview.qt-project.org/#/c/196614/, delta to Qt 5.9.0 as an attachment. RTA testing is ongoing and snapshot seems to be pretty much OK. So please test the snapshot & report your effort via https://wiki.qt.io/Qt59_release_testing And please note: We will do regular patch releases for 5.9 series and so on we won't block the release because of old issues. Qt 5.9.1 is released on June and 5.9.2 is targeted to be released on August so if there is still bad issues open in 5.9.1 there is time to fix those for soon coming Qt 5.9.2 (or even Qt 5.9.3 which should be out ~September...) br, Jani Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 From Simon.Hausmann at qt.io Wed Jun 21 08:47:18 2017 From: Simon.Hausmann at qt.io (Simon Hausmann) Date: Wed, 21 Jun 2017 06:47:18 +0000 Subject: [Releasing] First Qt 5.9.1 snapshot available In-Reply-To: <7FC8D04D3E708B4AA8248F6D64E0CB2136B860CC@IRSMSX104.ger.corp.intel.com> References: , <7FC8D04D3E708B4AA8248F6D64E0CB2136B860CC@IRSMSX104.ger.corp.intel.com> Message-ID: <39626165-55E6-4AD2-8014-7DFF199F13F3@qt.io> Hi, If my memory serves me right then it's a little magic :) You select the qqc in the installer and it will show - as version- the latest Qt version that a build is available for (like even a 5.9 snapshot). Behind the scenes however it would install binaries of the compiler for all Qt versions that you have selected, into the respective installation directories. The compiler is strictly tied to the Qt version, so a binary from 5.9 cannot be used with 5.7. However the installer should have placed a 5.7 compatible version into your Qt 5.7 directory if you have selected 5.8 and qqc. Note that at this point the binaries are target independent, so you can use the qqc binary for a Qt 5.7 Linux desktop build also for an arm Linux build for example. As long as the host binary runs :) Simon > On 19. Jun 2017, at 15:16, Bullinger, Julius wrote: > > Hi, > > Since there is only one global Qt Quick Compiler component, it seems like it will be updated to 5.9.1-0-201706131028 even if the snapshot is not installed. Is this intended behavior? > > Are the Qt Quick Compiler versions compatible between releases? Can I also use it with Qt 5.9.0? What about Qt 5.7.1? > > If not, is there a way to install an older version? > > Thanks and br, > Julius > > -----Original Message----- > From: Interest [mailto:interest-bounces+julius.bullinger=intel.com at qt-project.org] On Behalf Of Jani Heikkinen > Sent: Wednesday, June 14, 2017 08:01 > To: development at qt-project.org; interest at qt-project.org > Cc: releasing at qt-project.org > Subject: [Interest] First Qt 5.9.1 snapshot available > Importance: High > > Hi all, > > We have first Qt 5.9.1 snapshot available via online installer. It is a separate 5.9.1 node, not as an update to Qt 5.9.0. Instructions how to install it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer > > Content of the snapshot is based on https://codereview.qt-project.org/#/c/196614/, delta to Qt 5.9.0 as an attachment. > > RTA testing is ongoing and snapshot seems to be pretty much OK. So please test the snapshot & report your effort via https://wiki.qt.io/Qt59_release_testing > > And please note: We will do regular patch releases for 5.9 series and so on we won't block the release because of old issues. Qt 5.9.1 is released on June and 5.9.2 is targeted to be released on August so if there is still bad issues open in 5.9.1 there is time to fix those for soon coming Qt 5.9.2 (or even Qt 5.9.3 which should be out ~September...) > > br, > Jani > > > > Intel Deutschland GmbH > Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany > Tel: +49 89 99 8853-0, www.intel.de > Managing Directors: Christin Eisenschmid, Christian Lamprechter > Chairperson of the Supervisory Board: Nicole Lau > Registered Office: Munich > Commercial Register: Amtsgericht Muenchen HRB 186928 > > _______________________________________________ > Releasing mailing list > Releasing at qt-project.org > http://lists.qt-project.org/mailman/listinfo/releasing From jani.heikkinen at qt.io Wed Jun 21 11:39:52 2017 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 21 Jun 2017 09:39:52 +0000 Subject: [Releasing] First Qt 5.9.1 snapshot available In-Reply-To: <39626165-55E6-4AD2-8014-7DFF199F13F3@qt.io> References: , <7FC8D04D3E708B4AA8248F6D64E0CB2136B860CC@IRSMSX104.ger.corp.intel.com>, <39626165-55E6-4AD2-8014-7DFF199F13F3@qt.io> Message-ID: >> >>________________________________________ >>From: Releasing on behalf of Simon Hausmann >>Sent: Wednesday, June 21, 2017 9:47 AM >>To: Bullinger, Julius >>Cc: releasing at qt-project.org; interest at qt-project.org >>Subject: Re: [Releasing] First Qt 5.9.1 snapshot available >> >>Hi, >> >>If my memory serves me right then it's a little magic :) >> >>You select the qqc in the installer and it will show - as version- the latest Qt version that a build is available for (like even a 5.9 snapshot). Behind the scenes however it would install binaries of the compiler for all >>Qt versions that you have selected, into the respective installation directories. Yes, you remembered it right ;) br, Jani From julius.bullinger at intel.com Wed Jun 21 17:02:38 2017 From: julius.bullinger at intel.com (Bullinger, Julius) Date: Wed, 21 Jun 2017 15:02:38 +0000 Subject: [Releasing] First Qt 5.9.1 snapshot available In-Reply-To: <39626165-55E6-4AD2-8014-7DFF199F13F3@qt.io> References: , <7FC8D04D3E708B4AA8248F6D64E0CB2136B860CC@IRSMSX104.ger.corp.intel.com> <39626165-55E6-4AD2-8014-7DFF199F13F3@qt.io> Message-ID: <7FC8D04D3E708B4AA8248F6D64E0CB2136B86C01@IRSMSX104.ger.corp.intel.com> -----Original Message----- From: Simon Hausmann [mailto:Simon.Hausmann at qt.io] Sent: Wednesday, June 21, 2017 08:47 To: Bullinger, Julius Cc: interest at qt-project.org; releasing at qt-project.org Subject: Re: [Releasing] First Qt 5.9.1 snapshot available > Hi, > > If my memory serves me right then it's a little magic :) > > You select the qqc in the installer and it will show - as version- the latest Qt version that a build is > available for (like even a 5.9 snapshot). Behind the scenes however it would install binaries of the > compiler for all Qt versions that you have selected, into the respective installation directories. > > The compiler is strictly tied to the Qt version, so a binary from 5.9 cannot be used with 5.7. However > the installer should have placed a 5.7 compatible version into your Qt 5.7 directory if you have > selected 5.8 and qqc. I see, thanks for the explanation! Is this documented anywhere? If not, it should perhaps be. ;) Best regards, Julius Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 From akseli.salovaara at qt.io Mon Jun 26 17:28:26 2017 From: akseli.salovaara at qt.io (Akseli Salovaara) Date: Mon, 26 Jun 2017 15:28:26 +0000 Subject: [Releasing] New Qt 5.9.1 snapshot available Message-ID: Hi all, We have a new Qt 5.9.1 snapshot available via online installer. It is a separate Qt 5.9.1 node, not as an update to Qt 5.9.0, but will overwrite previous Qt 5.9.1 snapshot. Instructions how to install it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer Content of the snapshot is based on https://codereview.qt-project.org/197790, delta to Qt 5.9.0 as an attachment. RTA testing is ongoing and excluding fix for https://bugreports.qt.io/browse/QTBUG-61635 Android deployment issue this should be the final Qt 5.9.1 content. So please test the snapshot & report your effort via https://wiki.qt.io/Qt59_release_testing Br, Akseli -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Qt5.9.1-delta-Qt5.9.0.txt URL: From akseli.salovaara at qt.io Wed Jun 28 09:00:21 2017 From: akseli.salovaara at qt.io (Akseli Salovaara) Date: Wed, 28 Jun 2017 07:00:21 +0000 Subject: [Releasing] [Development] New Qt 5.9.1 snapshot available In-Reply-To: References: Message-ID: > -----Original Message----- > From: Kari Oikarinen > Sent: keskiviikko 28. kesäkuuta 2017 08:57 > To: Vincent Hui ; Akseli Salovaara > > Cc: development at qt-project.org; releasing at qt-project.org > Subject: Re: [Development] New Qt 5.9.1 snapshot available > > I believe this is https://bugreports.qt.io/browse/QTCREATORBUG-17909 > Correct. The index "2" or "3" on Qt Creator "Kits" or "Qt Versions" auto-detected labels has nothing to do with MSVC 2015 Update version. Qt 5.9.1 is built by MSVC2015 with Update 3. > -- > Kari > > On 28.06.2017 04:07, Vincent Hui wrote: > > Hi Akseli, > > > > Why Qt 5.9.1 for MSVC2015 version on Windows is label as "Qt 5.9.1 > > MSVC2015 64bit2"? That makes me think Qt 5.9.1 is built by MSVC2015 > > with update 2 not update 3. Qt 5.9.0 for MSVC2015 version on Windows > > is label as "Qt 5.9.0 MSVC2015 64bit3". By the number 3 after "64bit", > > I think Qt > > 5.9.0 is built by MSVC2015 with update 3. > > > > Is Qt 5.9.1 not built by MSVC2015 with update 3? > > > > Br, > > Vincent > > > > > > On Mon, Jun 26, 2017 at 11:28 PM, Akseli Salovaara > > > wrote: > > > > Hi all, > > > > We have a new Qt 5.9.1 snapshot available via online installer. It > > is a separate Qt 5.9.1 node, not as an update to Qt 5.9.0, but will > > overwrite previous Qt 5.9.1 snapshot. Instructions how to install it > > here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer > > > > > > Content of the snapshot is based on > > https://codereview.qt-project.org/197790 > > , delta to Qt 5.9.0 as an > > attachment. > > > > RTA testing is ongoing and excluding fix for > > https://bugreports.qt.io/browse/QTBUG-61635 > > Android deployment > > issue this should be the final Qt 5.9.1 content. So please test the > > snapshot & report your effort via > > https://wiki.qt.io/Qt59_release_testing > > > > > > Br, > > Akseli > > > > > > _______________________________________________ > > Development mailing list > > Development at qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development > > > > > > > > > > > > _______________________________________________ > > Development mailing list > > Development at qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development > > > > -- > --- > Kari Oikarinen > Software Engineer > > The Qt Company > Elektroniikkatie 13 > 90590, Oulu, Finland > kari.oikarinen at qt.io > +358 50 5281010 > http://qt.io > ---