From jani.heikkinen at qt.io Wed Aug 3 07:50:32 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 3 Aug 2016 05:50:32 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 02.08.2016 Message-ID: Meeting minutes from Qt Release Team meeting 2nd August 2016 5.8 branching and FF: - qt5.git integration hasn't succeed since 3rd July in 'dev'. We will wait until new qt5.git integration is merged before starting soft branching from 'dev' to '5.8' * That way we can get solid baseline for '5.8' and 'dev' & we will be quite close to Alpha release at FF * FF will happen one week from date when soft branching starts Qt 5.6.2 and Qt 5.7.1: - Target to create first snapshots for testing as soon as possible and agree the schedule after first test results available * most probably we will try to release both during September Next meeting 9th August 2016 16:00 CET br, Jani irc log below: [17:00:05] akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche: ping [17:00:41] pong [17:00:41] jaheikki3: pong [17:00:46] jaheikki3L: pong [17:00:57] jaheikki3: pong [17:02:29] Time to start qt release team meeting [17:02:33] On agenda today: [17:02:43] Qt 5.8 branching & FF [17:02:55] Any additional item to the agenda today? [17:03:36] 5.7.1 [17:04:15] 5.7.1+5.6.2? [17:04:19] what's the plan for those, yeah [17:05:08] carewolf: thiago: ok, we can shortly discuss those as well (even I am not yet fully in synch what is the status) [17:05:29] Let's start from 5.8 branching & FF: [17:05:56] It was targetted to start soft branching today & have FF for 5.8 9th August [17:06:31] Unfortunately qt5.git integration hasn't succeed in 'dev' since beginning of July, see https://codereview.qt-project.org/#/q/status:merged+project:qt/qt5+branch:dev,n,z [17:07:06] probably due to vacations [17:07:25] I guess that fixing that and getting reviews through is this "soft freeze" [17:07:31] I think it would be good to get qt5.git integrated in 'dev' before start branching. That way we would have solid base for '5.8' and 'dev' as well [17:07:35] but given that lots of people were away, we may need an extension [17:08:42] I agree we need to wait for the integration [17:08:48] how long does it usually take to resolve this issue? [17:10:18] thiago: it depends :) Sometimes it takes lots of time and sometimes it is easy. [17:11:21] lqi is finalizing merges from 5.7 -> to dev to make sure all needed fixes are in 'dev' as well. There is new changes in 'dev' all the time and that makes situation a bit harder but I hope we can get the integration passed during this week [17:11:38] ok [17:11:50] do you think the soft branch should wait until that happens? [17:12:10] thiago: I think so. [17:13:30] If we solve that in dev then we will have working base for '5.8' and 5.9 (='dev'). And in that case we should be pretty close to Alpha release in FF [17:13:54] So spending some time still in 'dev' should save our time in the future [17:14:03] I'd also really like to see RHEL 7 added for packaging [17:14:21] because our linux packages look bad - no gtk, no gstreamer 1.0 [17:15:01] fregl: I agree. I know tosaraja and sifalt are working on that but unfortunately I don't know the latest status [17:15:16] fregl: that's not blocking, since we don't create binaries for alpha [17:15:30] jaheikki3: agreed, we'll wait for the merge to be successful before 5.8 is created [17:15:37] and then FF happens one week from that date [17:15:38] thiago: not for the alpha, but the sooner the better [17:16:29] Yeah [17:16:56] I think this was all from 5.8 at this time [17:17:19] Then Qt 5.7.1 and Qt 5.6.2 status and plans [17:18:23] Qt5.git integration seems to be succeed in '5.7' today [17:18:39] and in '5.6' at the end of July [17:19:11] So we should be able to produce first binary snapshots for Qt 5.7.1 and Qt 5.6.2 quite soon [17:20:11] I think we should preparations to release Qt 5.7.1 quite soon, I would say at the beginning of September [17:21:02] And release Qt 5.6.2 after that, somewhere mid sep [17:21:47] At the moment I haven't checked the blocker lists for any of these but I'll start that immediately when we have first snapshots for testing [17:23:12] Let's wait first testing results first & then agree the branching and releasing schedules [17:23:21] Any comments or questions? [17:25:16] sounds good, though why no the other way: 5.6.2 then 5.7.1 [17:25:22] agreed [17:25:42] we'll need to think whether 5.6.3 & 5.7.2 are necessary before 5.8.0 final [17:25:49] bug-fixes that affect both should go to 5.6 branch and then merged to 5.7, so merging that way seems more natural [17:26:18] since 5.8.0 will be a long time from now, yes, we should have one [17:26:53] carewolf: well, true. It might be better to release 5.6.2 first... [17:27:27] Let's see that after we have some testing results available. [17:28:39] And what comes to 5.6.3 and 5.7.2: It might be that we need to release one or both before 5.8 final but we will see that later, after 5.6.2 and 5.7.1 releases [17:29:43] I hope we don't need to release those before 5.8 final but it might be possible if really needed [17:30:26] if there are lots of fixes for those, we should [17:30:27] Doing 4 path releases + 5.8 alpha, beta, rc and final before Christmas is quite much... [17:30:51] but the point is that we should think about it later [17:31:11] thiago: yeah, true. Let's check that a bit later [17:31:42] ok, I think this is all at this time. [17:32:04] Thanks for your participation. Bye! [17:32:32] wait [17:32:42] I wanted to ask if there's anything of 5.6.1-1 that needs discussing [17:33:06] anything we can learn from it, aside from "we need a process and will discuss @ QCS" ? [17:33:36] thiago: Yes, i think there is but I think we should postpone that discussion a bit to get more people back from the vacation [17:33:56] thiago: OK? [17:34:29] ok [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Mon Aug 8 12:57:30 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Mon, 8 Aug 2016 10:57:30 +0000 Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... Message-ID: Hi all, Qt5.git integration in 'dev' succeed during the weekend and we have soft branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th August 2016 as well as final branching from 'dev' to '5.8' So please start using '5.8' for changes targeted to Qt 5.8 release and finalize ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen Monday 15th Aug (morning). Please make sure - All new modules for Qt 5.8 are in 'dev' & part of qt5.git - All mandatory new features are in 'dev' now or coming in within a week? - New feature page contains all new features etc: https://wiki.qt.io/New_Features_in_Qt_5.8 We will create first src packages from latest qt5.git integration as soon as possible. Please check the packages immediately when available to see if something important is missing. Those packages should be quite close to Qt 5.8 alpha packages so it will be really important to check the packages now. br, Jani Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io +358 50 4873735 http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From iikka.eklund at qt.io Wed Aug 10 07:21:22 2016 From: iikka.eklund at qt.io (Iikka Eklund) Date: Wed, 10 Aug 2016 05:21:22 +0000 Subject: [Releasing] Apparent virus in qt downloads? In-Reply-To: <3685ed28-1e6f-f41d-2861-82a60aa06524@gmx.de> References: <1f809904-d118-a017-97ff-4d0bcdaf743f@gmx.de>

, <3685ed28-1e6f-f41d-2861-82a60aa06524@gmx.de> Message-ID: We've had quite a lot "virus/trojan detected" reports lately, all of which have turned out to be false positive as far I know? Are our hands tied here or is there any channel to report these false alarms to Avast/Symantec etc.? Iikka Eklund Senior Software Engineer The Qt Company Elektroniikkatie 13 90590, Oulu, Finland iikka.eklund at qt.io http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] ________________________________ From: Releasing on behalf of Daniel Sent: Thursday, July 7, 2016 11:06:18 AM To: Kai Koehne; releasing at qt-project.org Subject: Re: [Releasing] Apparent virus in qt downloads? Hi, Avast just warned me again. This time for a file already installed. I have attached a screenshot that contains the filename. I went on to do a smart scan and avast did not detect a virus. Best Daniel On 06.07.2016 09:33, Kai Koehne wrote: > It doesn't seem to complain about the installer executable itself, but about an archive that's fetched online. > > Does it tell you more if you select 'Smart Scan ausführen'? > > Regards > > Kai > >> -----Original Message----- >> From: Daniel [mailto:xracoonx at gmx.de] >> Sent: Wednesday, July 06, 2016 9:27 AM >> To: Kai Koehne ; releasing at qt-project.org >> Subject: Re: [Releasing] Apparent virus in qt downloads? >> >> Hi, >> >> Unfortunately, avast seems not provide those details in the logs. It only >> mentions the qt online installer. I could try the download again. >> Can I extract the information from the qt online installer somehow? >> >> Daniel >> >> On 06.07.2016 09:19, Kai Koehne wrote: >>> Hi, >>> >>> Would be still interesting to know which file it is complaining about ... Any >> chance you can get the full path + maybe the m5sum of the file in question? >>> >>> Thanks >>> >>> Kai >>> >>>> -----Original Message----- >>>> From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io at qt- >>>> project.org] On Behalf Of Daniel >>>> Sent: Wednesday, July 06, 2016 9:05 AM >>>> To: releasing at qt-project.org >>>> Subject: [Releasing] Apparent virus in qt downloads? >>>> >>>> Hi, >>>> >>>> I just tried to download x86 windows 7 qt via the unified installer >>>> but it did not succeed because of a virus warning (screenshot attached). >>>> >>>> Daniel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Simo.Falt at qt.io Wed Aug 10 07:29:47 2016 From: Simo.Falt at qt.io (=?utf-8?B?U2ltbyBGw6RsdA==?=) Date: Wed, 10 Aug 2016 05:29:47 +0000 Subject: [Releasing] Apparent virus in qt downloads? In-Reply-To: References: <1f809904-d118-a017-97ff-4d0bcdaf743f@gmx.de>

<3685ed28-1e6f-f41d-2861-82a60aa06524@gmx.de> Message-ID: <1A0E930B-330F-4E7D-B51D-C7E7513B8F8B@qt.io> At least Symantec offers this: https://submit.symantec.com/false_positive/ But I’m not sure how seriously they take these. And that is only Symantec… Simo From: Releasing on behalf of Iikka Eklund Date: Wednesday 10 August 2016 08:21 To: Kai Koehne , "releasing at qt-project.org" , Wiglaf Cai , Jani Heikkinen Subject: Re: [Releasing] Apparent virus in qt downloads? We've had quite a lot "virus/trojan detected" reports lately, all of which have turned out to be false positive as far I know? Are our hands tied here or is there any channel to report these false alarms to Avast/Symantec etc.? Iikka Eklund Senior Software Engineer The Qt Company Elektroniikkatie 13 90590, Oulu, Finland iikka.eklund at qt.io http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] ________________________________ From: Releasing on behalf of Daniel Sent: Thursday, July 7, 2016 11:06:18 AM To: Kai Koehne; releasing at qt-project.org Subject: Re: [Releasing] Apparent virus in qt downloads? Hi, Avast just warned me again. This time for a file already installed. I have attached a screenshot that contains the filename. I went on to do a smart scan and avast did not detect a virus. Best Daniel On 06.07.2016 09:33, Kai Koehne wrote: > It doesn't seem to complain about the installer executable itself, but about an archive that's fetched online. > > Does it tell you more if you select 'Smart Scan ausführen'? > > Regards > > Kai > >> -----Original Message----- >> From: Daniel [mailto:xracoonx at gmx.de] >> Sent: Wednesday, July 06, 2016 9:27 AM >> To: Kai Koehne ; releasing at qt-project.org >> Subject: Re: [Releasing] Apparent virus in qt downloads? >> >> Hi, >> >> Unfortunately, avast seems not provide those details in the logs. It only >> mentions the qt online installer. I could try the download again. >> Can I extract the information from the qt online installer somehow? >> >> Daniel >> >> On 06.07.2016 09:19, Kai Koehne wrote: >>> Hi, >>> >>> Would be still interesting to know which file it is complaining about ... Any >> chance you can get the full path + maybe the m5sum of the file in question? >>> >>> Thanks >>> >>> Kai >>> >>>> -----Original Message----- >>>> From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io at qt- >>>> project.org] On Behalf Of Daniel >>>> Sent: Wednesday, July 06, 2016 9:05 AM >>>> To: releasing at qt-project.org >>>> Subject: [Releasing] Apparent virus in qt downloads? >>>> >>>> Hi, >>>> >>>> I just tried to download x86 windows 7 qt via the unified installer >>>> but it did not succeed because of a virus warning (screenshot attached). >>>> >>>> Daniel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kai.Koehne at qt.io Fri Aug 12 15:03:18 2016 From: Kai.Koehne at qt.io (Kai Koehne) Date: Fri, 12 Aug 2016 13:03:18 +0000 Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... In-Reply-To: References: Message-ID: 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 WebEngine even after Monday morning. The features still waiting to get merged are Printing: https://codereview.qt-project.org/#/c/162928/ and following Printing of CSS backgrounds: https://codereview.qt-project.org/#/c/167484/ Support for certificate transparency: https://codereview.qt-project.org/#/c/167275/ Support for custom QML context menu/ dialogs: https://codereview.qt-project.org/#/c/162263/, https://codereview.qt-project.org/#/c/165731/ Support for Qt Quick 2 Controls dialogs: https://codereview.qt-project.org/#/c/162262/ Regards Kai > -----Original Message----- > From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io at qt- > project.org] On Behalf Of Jani Heikkinen > Sent: Monday, August 08, 2016 12:58 PM > To: development at qt-project.org > Cc: releasing at qt-project.org > Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 > Feature Freeze coming... > > Hi all, > > > > > Qt5.git integration in 'dev' succeed during the weekend and we have soft > branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th > August 2016 as well as final branching from 'dev' to '5.8' > > > > > > So please start using '5.8' for changes targeted to Qt 5.8 release and finalize > ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen > Monday 15th Aug (morning). > > > > > Please make sure > > > - All new modules for Qt 5.8 are in 'dev' & part of qt5.git > > > - All mandatory new features are in 'dev' now or coming in within a week? > > > - New feature page contains all new features etc: > https://wiki.qt.io/New_Features_in_Qt_5.8 > > > > > We will create first src packages from latest qt5.git integration as soon as > possible. Please check the packages immediately when available to see if > something important is missing. Those packages should be quite close to Qt > 5.8 alpha packages so it will be really important to check the packages now. > > > > > br, > > Jani > > > > > > Jani Heikkinen > Release Manager > > The Qt Company > Elektroniikkatie 13 > 90590 Oulu Finland > jani.heikkinen at qt.io > +358 50 4873735 > http://qt.io > > > > > > > > > From Simon.Hausmann at qt.io Fri Aug 12 21:31:25 2016 From: Simon.Hausmann at qt.io (Simon Hausmann) Date: Fri, 12 Aug 2016 19:31:25 +0000 Subject: [Releasing] [Development] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... In-Reply-To: References: , Message-ID: Hi, I totally support Kai's request. On the upside: The qtlocation build is fixed :) Simon ________________________________ From: Development on behalf of Kai Koehne Sent: Friday, August 12, 2016 3:03:18 PM To: Jani Heikkinen; development at qt-project.org Cc: releasing at qt-project.org Subject: 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 WebEngine even after Monday morning. The features still waiting to get merged are Printing: https://codereview.qt-project.org/#/c/162928/ and following Printing of CSS backgrounds: https://codereview.qt-project.org/#/c/167484/ Support for certificate transparency: https://codereview.qt-project.org/#/c/167275/ Support for custom QML context menu/ dialogs: https://codereview.qt-project.org/#/c/162263/, https://codereview.qt-project.org/#/c/165731/ Support for Qt Quick 2 Controls dialogs: https://codereview.qt-project.org/#/c/162262/ Regards Kai > -----Original Message----- > From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io at qt- > project.org] On Behalf Of Jani Heikkinen > Sent: Monday, August 08, 2016 12:58 PM > To: development at qt-project.org > Cc: releasing at qt-project.org > Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 > Feature Freeze coming... > > Hi all, > > > > > Qt5.git integration in 'dev' succeed during the weekend and we have soft > branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th > August 2016 as well as final branching from 'dev' to '5.8' > > > > > > So please start using '5.8' for changes targeted to Qt 5.8 release and finalize > ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen > Monday 15th Aug (morning). > > > > > Please make sure > > > - All new modules for Qt 5.8 are in 'dev' & part of qt5.git > > > - All mandatory new features are in 'dev' now or coming in within a week? > > > - New feature page contains all new features etc: > https://wiki.qt.io/New_Features_in_Qt_5.8 > > > > > We will create first src packages from latest qt5.git integration as soon as > possible. Please check the packages immediately when available to see if > something important is missing. Those packages should be quite close to Qt > 5.8 alpha packages so it will be really important to check the packages now. > > > > > br, > > Jani > > > > > > Jani Heikkinen > Release Manager > > The Qt Company > Elektroniikkatie 13 > 90590 Oulu Finland > jani.heikkinen at qt.io > +358 50 4873735 > http://qt.io > > > > > > > > > _______________________________________________ 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 Sat Aug 13 14:03:45 2016 From: lars.knoll at qt.io (Lars Knoll) Date: Sat, 13 Aug 2016 12:03:45 +0000 Subject: [Releasing] [Development] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... In-Reply-To: References: Message-ID: <5A45BDD7-4AA0-44BA-A389-AA30EE8DE5D0@qt.io> Sounds good to me. We'll also need some days past the feature free to get the remaining changes to the configuration system merged. Cheers, Lars On 12 Aug 2016, at 21:31, Simon Hausmann > wrote: Hi, I totally support Kai's request. On the upside: The qtlocation build is fixed :) Simon ________________________________ From: Development > on behalf of Kai Koehne > Sent: Friday, August 12, 2016 3:03:18 PM To: Jani Heikkinen; development at qt-project.org Cc: releasing at qt-project.org Subject: 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 WebEngine even after Monday morning. The features still waiting to get merged are Printing: https://codereview.qt-project.org/#/c/162928/ and following Printing of CSS backgrounds: https://codereview.qt-project.org/#/c/167484/ Support for certificate transparency: https://codereview.qt-project.org/#/c/167275/ Support for custom QML context menu/ dialogs: https://codereview.qt-project.org/#/c/162263/, https://codereview.qt-project.org/#/c/165731/ Support for Qt Quick 2 Controls dialogs: https://codereview.qt-project.org/#/c/162262/ Regards Kai > -----Original Message----- > From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Jani Heikkinen > Sent: Monday, August 08, 2016 12:58 PM > To: development at qt-project.org > Cc: releasing at qt-project.org > Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 > Feature Freeze coming... > > Hi all, > > > > > Qt5.git integration in 'dev' succeed during the weekend and we have soft > branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th > August 2016 as well as final branching from 'dev' to '5.8' > > > > > > So please start using '5.8' for changes targeted to Qt 5.8 release and finalize > ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen > Monday 15th Aug (morning). > > > > > Please make sure > > > - All new modules for Qt 5.8 are in 'dev' & part of qt5.git > > > - All mandatory new features are in 'dev' now or coming in within a week? > > > - New feature page contains all new features etc: > https://wiki.qt.io/New_Features_in_Qt_5.8 > > > > > We will create first src packages from latest qt5.git integration as soon as > possible. Please check the packages immediately when available to see if > something important is missing. Those packages should be quite close to Qt > 5.8 alpha packages so it will be really important to check the packages now. > > > > > br, > > Jani > > > > > > Jani Heikkinen > Release Manager > > The Qt Company > Elektroniikkatie 13 > 90590 Oulu Finland > jani.heikkinen at qt.io > +358 50 4873735 > http://qt.io > > > > > > > > > _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Releasing mailing list Releasing at qt-project.org http://lists.qt-project.org/mailman/listinfo/releasing -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Mon Aug 15 10:46:22 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Mon, 15 Aug 2016 08:46:22 +0000 Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... In-Reply-To: References: , Message-ID: Hi, Unfortunately we have challenges again with qt5.git integration in 'dev' and we need to wait that until we can do the feature freeze and final branching. So there might be still time to get these in as well before ff. br, Jani ________________________________ From: Kai Koehne Sent: Friday, August 12, 2016 4:03 PM To: Jani Heikkinen; development at qt-project.org Cc: releasing at qt-project.org Subject: RE: [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 WebEngine even after Monday morning. The features still waiting to get merged are Printing: https://codereview.qt-project.org/#/c/162928/ and following Printing of CSS backgrounds: https://codereview.qt-project.org/#/c/167484/ Support for certificate transparency: https://codereview.qt-project.org/#/c/167275/ Support for custom QML context menu/ dialogs: https://codereview.qt-project.org/#/c/162263/, https://codereview.qt-project.org/#/c/165731/ Support for Qt Quick 2 Controls dialogs: https://codereview.qt-project.org/#/c/162262/ Regards Kai > -----Original Message----- > From: Releasing [mailto:releasing-bounces+kai.koehne=qt.io at qt- > project.org] On Behalf Of Jani Heikkinen > Sent: Monday, August 08, 2016 12:58 PM > To: development at qt-project.org > Cc: releasing at qt-project.org > Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 > Feature Freeze coming... > > Hi all, > > > > > Qt5.git integration in 'dev' succeed during the weekend and we have soft > branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th > August 2016 as well as final branching from 'dev' to '5.8' > > > > > > So please start using '5.8' for changes targeted to Qt 5.8 release and finalize > ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen > Monday 15th Aug (morning). > > > > > Please make sure > > > - All new modules for Qt 5.8 are in 'dev' & part of qt5.git > > > - All mandatory new features are in 'dev' now or coming in within a week? > > > - New feature page contains all new features etc: > https://wiki.qt.io/New_Features_in_Qt_5.8 > > > > > We will create first src packages from latest qt5.git integration as soon as > possible. Please check the packages immediately when available to see if > something important is missing. Those packages should be quite close to Qt > 5.8 alpha packages so it will be really important to check the packages now. > > > > > br, > > Jani > > > > > > Jani Heikkinen > Release Manager > > The Qt Company > Elektroniikkatie 13 > 90590 Oulu Finland > jani.heikkinen at qt.io > +358 50 4873735 > http://qt.io > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Tue Aug 16 17:13:53 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 16 Aug 2016 15:13:53 +0000 Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... In-Reply-To: References: Message-ID: Hi all, We have still issues with qt5.git integration in 'dev' and some configuration system related changes are missing as well. That's why we agreed to postpone final branching (&FF) a bit in today's release team meeting (memo coming later). New target is Monday 22nd August 2016. Please do not merge new stuff into dev (that's not strictly required for 5.8) at this point to help us with qt5.git integration. Especially please avoid changes to public or internal APIs for this one week. Br, Jani From: Jani Heikkinen Sent: 8. elokuuta 2016 13:58 To: development at qt-project.org Cc: releasing at qt-project.org Subject: HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... Hi all, Qt5.git integration in 'dev' succeed during the weekend and we have soft branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th August 2016 as well as final branching from 'dev' to '5.8' So please start using '5.8' for changes targeted to Qt 5.8 release and finalize ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen Monday 15th Aug (morning). Please make sure - All new modules for Qt 5.8 are in 'dev' & part of qt5.git - All mandatory new features are in 'dev' now or coming in within a week? - New feature page contains all new features etc: https://wiki.qt.io/New_Features_in_Qt_5.8 We will create first src packages from latest qt5.git integration as soon as possible. Please check the packages immediately when available to see if something important is missing. Those packages should be quite close to Qt 5.8 alpha packages so it will be really important to check the packages now. br, Jani Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io +358 50 4873735 http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Wed Aug 17 11:33:54 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 17 Aug 2016 09:33:54 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 16.08.2016 Message-ID: Meeting minutes from Qt Release Team meeting 16th August 2016 Qt 5.8.0 status: - branching ongoing. Qt5.git integration failing in 'dev' and some important changes still missing --> we need to postpone FF & final branching a bit * Please do not merge new changes in 'dev' at this point to make qt5.git integration easier & save the resources (there is already '5.8' branch for important 5.8 changes). Especially please avoid changes to public or internal APIs. - New target for FF and final branching Mon 22nd August 2016 - New TP modules (qtnetworkauth & qtspeech) not in yet. Hoping we can get those in before FF but we won't wait those (can be added later in '5.8'). Qt 5.6.2 and Qt 5.7.1 status: - No real progress since last meeting [☹] * No snapshot available for testing, some binaries were missing. Should be fixed now, just waiting for qt5.git integration to succeed. - Target to release both as soon as possible (hoping during September) Next meeting Tue 23rd August 2016 16:00 CET br, Jani irc log below: [17:01:21] akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche: ping [17:01:26] jaheikki3: pong [17:04:14] jaheikki3: pong [17:04:24] time to start qt release team meeting [17:04:33] On agenda today [17:04:48] Qt 5.8.0 status [17:05:03] Qt 5.6.2 & Qt 5.7.1 status [17:05:15] Any additional item to the agenda? [17:07:09] Lets start from Qt 5.8.0 status: [17:08:14] - Branching ongoing. Unfortunately qt5.git hasn't integrated since we started the soft branching --> we cannot finalize the branching & do the FF at the moment [17:08:49] ok [17:08:53] is that the only thing missing? [17:09:25] - There is also couple of new TP modules which aren't in qt5.git yet, see https://codereview.qt-project.org/#/c/168023/ & https://codereview.qt-project.org/#/c/162697/ [17:10:45] qtnetworkauth is a really recent addition [17:10:48] let's not stop for it [17:11:01] It would be good to get those in as well. And kkoehne reported some changes still missing, see http://lists.qt-project.org/pipermail/releasing/2016-August/004320.html [17:11:02] we can add it at any time, even with disabled builds [17:11:15] I don't remember qtspeech request to be added. Must be old. [17:12:21] thiago: Yes, that is true. But it would be easiest if those would be in at FF. But I agree, let's not wait those but add later when all ok [17:12:40] it would be easiest, but we can't wait for them [17:12:45] yeah [17:13:07] what's happening with qt5.git? [17:13:25] failing tests? flaky or reliably failing? [17:13:25] And lars also mailed about missing configuration system changes, see http://lists.qt-project.org/pipermail/releasing/2016-August/004322.html [17:13:30] or is it even compilation errors? [17:14:35] thiago: some issues with tests [17:14:58] thiago: Actually almost all possible :( There were compilation issue which is fixed now. Latest one was failing test. We have blacklisted it because we need fregl to fix it: It is caused by some change he knows... [17:14:58] see https://codereview.qt-project.org/#/c/165745/ [17:15:01] lars: how complex are the feature system changes that are left? [17:15:02] thiago: mainly related to the touch handling change. but I think it's under control now (unfortunately fregl is on vacation right now) [17:15:14] thiago: unfortunately not trivial [17:15:34] lars: what would happen if we didn't add them at all to 5.8? [17:16:01] no go. it's one of the central features we need for the embedded side [17:16:30] but if the feature isn't ready for feature freeze... [17:16:49] how much longer? [17:16:58] the unit tests are still failing, so we're not at FF [17:17:28] I hope that we get it in within the next 1-2 days. I've done test runs in CI to iron out all issues, only one left [17:18:21] ok [17:18:41] should be fine then, same time as the test [17:18:55] I hope so. we really need that one [17:19:02] how long after the test passes that we can call FF? [17:19:07] Ok, it seems we need to postpone ff a bit. I propose that we try to get things ready during this week & have FF next monday (if we managed to integrate qt5.git & get conf changes in) [17:19:34] What about those kkoehne's changes? [17:19:58] jaheikki3: let's work towards that. but if we get the config changes in and have a qt5.git integration with those, I'd simply freeze from there [17:20:14] jaheikki3: those are webengine only, right? [17:20:32] lars: Yes [17:20:54] we need to merge dev and 5.8 again [17:21:04] jaheikki3: I'd say we go ahead and branch when we can. if there's something left, he needs to retarget to 5.8. [17:21:16] yeah [17:21:24] thiago: Yes, that is missing as well. It will be done at same time when we will have the FF [17:21:28] but we need an official cut-off for dev branch [17:21:40] shall we do this ASAP? [17:21:56] everything that wants to be on the other side of the FF needs to be retargetted now [17:22:04] thiago: I want to get qt5.git integrated there at first [17:22:17] Make things easier later [17:22:26] integrated in dev? [17:22:29] yes [17:22:48] yeah, but that doesn't help people knowing when it will happen [17:23:14] I'm asking if we should advise people to retarget from dev to 5.8 in the modules if their changes want to be in 5.8 [17:23:28] dev changes may, at any moment, no longer land in 5.8 [17:23:33] That's true. But people should use '5.8' already now for new changes & only finalize ongoing ones in 'dev' [17:23:51] the problem is that finalisation [17:24:04] lots of people (including me) are doing that and assuming that they're still in 5.8 [17:24:15] we need a specific point in time when that won't be the case any more [17:24:24] it can't be "any moment now" [17:26:20] can we have a more definite date? [17:26:26] Hmm, i somehow disagree but understand your point [17:28:05] shall we say next Monday? [17:28:18] anything that is in dev after next Monday risks not being in 5.8 [17:28:38] thiago: That is OK for me. [17:28:54] ok [17:29:40] ok, that should give us enough time for the configuration changes as well. [17:29:58] great [17:30:03] but let's not delay further. [17:30:07] agree [17:30:30] it is next monday, lets make sure all needed is ready at that point [17:31:00] Ok, it is all about 5.8 at this time [17:31:13] and let's ask people again to not merge new stuff into dev that's not strictly required for 5.8 at this point. those changes can wait for one week [17:31:41] lars: Yes, I'll do that [17:31:46] jaheikki3: thanks [17:31:57] Then Qt 5.6.1 and Qt 5.7.1 status [17:32:08] jaheikki3: especially no changes to public or internal APIs for this one week [17:32:36] to avoid further qt5.git issues [17:32:40] Yeah [17:33:27] - Unfortunately no real progress with Qt 5.6.2 or Qt 5.7.1 releases since last meeting :( [17:33:50] We tried to create first snapshots but noticed some binaries were missing [17:34:41] That was caused by some change in CI system. It is now fixed but we need to get new qt5.git integrations to get the binaries [17:36:16] Next tries during next night, hoping those will succeed to be able to create the snapshots for testing [17:36:32] what's our target [17:36:35] release ASAP? [17:36:49] thiago: I would say yes [17:36:53] ok [17:36:57] that's good info [17:37:10] I'd been prioritising 5.8 stuff, but I need to get back to fixing 5.6 now [17:37:13] But we need to get first snapshot for testing to see where we are [17:37:34] true [17:38:53] I think it was all about 5.6.2 & 5.7.1 [17:39:19] Is there something else at this time or should we end the meeting now & have new next tue? [17:40:18] are we planning a 5.7.2? [17:40:31] that is, when can we declare 5.7 dead? [17:41:21] very ideally, branch n-1 should be closed before n is branched as long as there is a LTS.. [17:41:43] fkleint: we need to agree that later [17:42:05] we should release 5.7.x until we have 5.8.0 [17:42:08] then we can stop [17:42:33] hm [17:43:47] lets check that after we have released 5.7.1 [17:44:03] m,ok [17:44:59] Ok, I need to go now. so let's end this meeting now. thank & bye [17:45:06] bye Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io +358 50 4873735 http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OutlookEmoji-☹.png Type: image/png Size: 506 bytes Desc: OutlookEmoji-☹.png URL: From oswald.buddenhagen at qt.io Mon Aug 22 17:10:48 2016 From: oswald.buddenhagen at qt.io (Oswald Buddenhagen) Date: Mon, 22 Aug 2016 17:10:48 +0200 Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... In-Reply-To: References: Message-ID: <20160822151048.GM3560@troll08> the final downmerge from dev to 5.8 is now completed. 5.8 is now officially feature-frozen, approved exceptions notwithstanding. dev is 5.9 material now. as usual, cherry-picks only with a *really* good justification _and_ bribe/sacrifice. get your 5.8 must-have changes re-targeted *before* integrating. On Tue, Aug 16, 2016 at 03:13:53PM +0000, Jani Heikkinen wrote: > Hi all, > > We have still issues with qt5.git integration in 'dev' and some configuration system related changes are missing as well. That's why we agreed to postpone final branching (&FF) a bit in today's release team meeting (memo coming later). New target is Monday 22nd August 2016. > > Please do not merge new stuff into dev (that's not strictly required for 5.8) at this point to help us with qt5.git integration. Especially please avoid changes to public or internal APIs for this one week. > > Br, > Jani > > From: Jani Heikkinen > Sent: 8. elokuuta 2016 13:58 > To: development at qt-project.org > Cc: releasing at qt-project.org > Subject: HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming... > > > Hi all, > > > > Qt5.git integration in 'dev' succeed during the weekend and we have soft branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th August 2016 as well as final branching from 'dev' to '5.8' > > > > So please start using '5.8' for changes targeted to Qt 5.8 release and finalize ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen Monday 15th Aug (morning). > > > > Please make sure > > - All new modules for Qt 5.8 are in 'dev' & part of qt5.git > > - All mandatory new features are in 'dev' now or coming in within a week? > > - New feature page contains all new features etc: https://wiki.qt.io/New_Features_in_Qt_5.8 > > > > We will create first src packages from latest qt5.git integration as soon as possible. Please check the packages immediately when available to see if something important is missing. Those packages should be quite close to Qt 5.8 alpha packages so it will be really important to check the packages now. > > > br, > Jani > > > > Jani Heikkinen > Release Manager > > The Qt Company > Elektroniikkatie 13 > 90590 Oulu Finland > jani.heikkinen at qt.io > +358 50 4873735 > http://qt.io > > > > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] > > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] > > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] > > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] > > [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] > > > _______________________________________________ > Releasing mailing list > Releasing at qt-project.org > http://lists.qt-project.org/mailman/listinfo/releasing From jani.heikkinen at qt.io Wed Aug 24 11:35:24 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 24 Aug 2016 09:35:24 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 23.08.2016 Message-ID: Meeting minutes from Qt Release Team meeting 23rd August 2016 Qt 5.8.0 Alpha status: - Branching now complete and FF is in effect - qt5.git integration has some issue(s) in '5.8', fixing ongoing - We will create alpha src packages for testing immediately after qt5.git integration succeed in '5.8' - Target is to release Qt 5.8.0 alpha during next week Qt 5.6.2: - First snapshot under testing * Please make sure all open release blockers are visible in https://bugreports.qt.io/issues/?filter=17829 - Target is to release Qt 5.6.2 as soon as possible * Target to start branching from '5.6' to '5.6.2' today Qt 5.7.1: - We will postpone the branching a while to get all fixes from 5.6.2 to 5.7 before branching - Target is to create first qt5.7.1 snapshot for testing soon * we have prioritized qt5.6.2 & 5.8.0 alpha and that's why no snapshot yet New meeting Tue 23rd August 2016 16:00 CET br, Jani irc log below: [16:59:56] akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche: ping [17:00:05] hello :) [17:00:08] jaheikki3: pong [17:00:55] jaheikki3: pong [17:01:43] Time to start qt release team meeting [17:01:46] jaheikki3: pong [17:01:52] On agenda today: [17:02:05] - qt 5.8.0 alpha status [17:02:12] - qt 5.6.2 status [17:02:19] -qt 5.7.1 status [17:02:29] Any additional item to the agenda? [17:02:43] will be back in 15-20 mins, picking up kids. but like to see https://codereview.qt-project.org/#/c/168824/ in 5.6.2 [17:04:13] Lets start from 5.8 alpha status [17:04:30] Branching is now complete and FF is in effect [17:04:49] berore alpha we need to get qt5.git integrated in '5.8' [17:05:12] Currently it seems qtspeech has some license header missing [17:05:32] jaheikki3: is there a bug for that? I wasn't aware of that [17:05:49] No, I just noticed that [17:06:05] see https://codereview.qt-project.org/#/c/168795/ [17:06:23] I just saw that qtspeech is not built on macOS either - kind of problematic [17:06:45] weird about the license test - that was fixed [17:07:38] fregl: ok, but qtspeech is TP and so on that shouldn't matter at this point. Of course should be fixed but shouldn't block the alpha [17:08:08] I'll check what the problem is - probably needs a patch from the dev branch in 5.8 [17:08:19] fregl: ok, thanks! [17:09:01] And when we get qt5.git integrated in '5.8' we will export alpha candidate src packages for testing [17:09:12] lars: Is the build sys now FF-ready? ..there is also stuff like https://bugreports.qt.io/browse/QTBUG-55455 .. [17:09:50] And if packages seems to be ok for alpha we are targeting to release it during next week [17:11:17] fkleint: lars: according to my understanding needed build system changes should be in. lars, correct if I have understood wrongly [17:11:28] Any other comments or questions? [17:13:38] Ok, thats all about 5.8 alpha at this time. Let's get qt5.git integrates as soon as possible to get alpha out as planned [17:13:48] then Qt 5.6.2 status: [17:14:08] first snapshot under testing at the moment [17:14:36] Some feedback already got but more needed [17:15:14] -*- thiago has an important QtDBus crash to solve [17:15:21] Packages seems to be quite good but there is some blockers left to be fixed before we can release [17:15:28] I've solved it, but can't integrate because it causes a different regression [17:15:43] thiago: is there a bug report about that? [17:16:41] current blocker list here: https://bugreports.qt.io/browse/QTBUG-55367?filter=17829 [17:16:55] please make sure all blockers are visible in that list [17:17:13] yes, several [17:17:17] not sure I should call it a blocker [17:17:29] it's a crash-at-exit [17:17:46] and I haven't been able to fix the other regression in two months [17:19:01] ok [17:19:32] I'm just mentioning if someone later complains that we released without fixing it [17:20:29] For me it seems we could start branching '5.6.2' from '5.6' and fix remaining blockers in the release branch. That way we could get 5.6.2 out quite soon. Any objections? [17:20:49] none from me [17:23:06] ok, lets start branching soon. I'll discuss tomorrow with ossi|tt... [17:23:24] That was all about 5.6.2 at this time. Then Qt 5.7.1: [17:23:47] qt5.git integration succeed last week [17:24:16] but we haven't created snapshot from that [17:24:34] we prioritize 5.6.2 & 5.8.0 [17:24:53] 5.6.2 should come before 5.7.1 [17:25:15] preferably, all fixes in 5.6.2 should be up-merged into 5.7 before the branching [17:25:19] so, yes, postpone [17:25:36] Yeah, that's why we haven't kept so much hurry with it [17:26:30] thiago: That makes sense. Let's agree we branch 5.7.1 from 5.7 after 5.6.2 changes are in '5.7' [17:26:48] Makes merges etc easier [17:27:23] But we are targeting to create 5.7.1 snapshot for testing soon to see where we are [17:28:08] that's good [17:28:21] That's all about 5.7.1. Any other comments or questions? [17:31:13] Ok, it was all at this time. Is there something else or should we just end this meeting now? [17:32:20] not from me.. [17:32:42] thanks, sounds good to me, I'm very happy about the order - 5.6 before the next 5.7 release :) [17:32:51] same here [17:33:28] Great! Lets end now & have new meeting next tue as planned. Thanks for your participation! [17:33:31] Bye [17:33:35] Bye Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io +358 50 4873735 http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: