[Releasing] Meeting minutes from Qt Release Team meeting 16.08.2016

Wed Aug 17 11:33:54 CEST 2016

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] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche: ping
[17:01:26] <thiago_> jaheikki3: pong
[17:04:14] <fkleint> jaheikki3: pong
[17:04:24] <jaheikki3> time to start qt release team meeting
[17:04:33] <jaheikki3> On agenda today
[17:04:48] <jaheikki3> Qt 5.8.0 status
[17:05:03] <jaheikki3> Qt 5.6.2 & Qt 5.7.1 status
[17:05:15] <jaheikki3> Any additional item to the agenda?
[17:07:09] <jaheikki3> Lets start from Qt 5.8.0 status:
[17:08:14] <jaheikki3> - 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] <thiago> ok
[17:08:53] <thiago> is that the only thing missing?
[17:09:25] <jaheikki3> - 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] <thiago> qtnetworkauth is a really recent addition
[17:10:48] <thiago> let's not stop for it
[17:11:01] <jaheikki3> 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] <thiago> we can add it at any time, even with disabled builds
[17:11:15] <thiago> I don't remember qtspeech request to be added. Must be old.
[17:12:21] <jaheikki3> 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] <thiago> it would be easiest, but we can't wait for them
[17:12:45] <jaheikki3> yeah
[17:13:07] <thiago> what's happening with qt5.git?
[17:13:25] <thiago> failing tests? flaky or reliably failing?
[17:13:25] <jaheikki3> And lars also mailed about missing configuration system changes, see http://lists.qt-project.org/pipermail/releasing/2016-August/004322.html
[17:13:30] <thiago> or is it even compilation errors?
[17:14:35] <lars> thiago: some issues with tests
[17:14:58] <jaheikki3> 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] <fkleint> see https://codereview.qt-project.org/#/c/165745/
[17:15:01] <thiago> lars: how complex are the feature system changes that are left?
[17:15:02] <lars> 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] <lars> thiago: unfortunately not trivial
[17:15:34] <thiago> lars: what would happen if we didn't add them at all to 5.8?
[17:16:01] <lars> no go. it's one of the central features we need for the embedded side
[17:16:30] <thiago> but if the feature isn't ready for feature freeze...
[17:16:49] <thiago> how much longer?
[17:16:58] <thiago> the unit tests are still failing, so we're not at FF
[17:17:28] <lars> 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] <thiago> ok
[17:18:41] <thiago> should be fine then, same time as the test
[17:18:55] <lars> I hope so. we really need that one
[17:19:02] <thiago> how long after the test passes that we can call FF?
[17:19:07] <jaheikki3> 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] <jaheikki3> What about those kkoehne's changes?
[17:19:58] <lars> 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] <lars> jaheikki3: those are webengine only, right?
[17:20:32] <jaheikki3> lars: Yes
[17:20:54] <thiago> we need to merge dev and 5.8 again
[17:21:04] <lars> 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] <thiago> yeah
[17:21:24] <jaheikki3> thiago: Yes, that is missing as well. It will be done at same time when we will have the FF
[17:21:28] <thiago> but we need an official cut-off for dev branch
[17:21:40] <thiago> shall we do this ASAP?
[17:21:56] <thiago> everything that wants to be on the other side of the FF needs to be retargetted now
[17:22:04] <jaheikki3> thiago: I want to get qt5.git integrated there at first
[17:22:17] <jaheikki3> Make things easier later
[17:22:26] <thiago> integrated in dev?
[17:22:29] <jaheikki3> yes
[17:22:48] <thiago> yeah, but that doesn't help people knowing when it will happen
[17:23:14] <thiago> 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] <thiago> dev changes may, at any moment, no longer land in 5.8
[17:23:33] <jaheikki3> That's true. But people should use '5.8' already now for new changes & only finalize ongoing ones in 'dev'
[17:23:51] <thiago> the problem is that finalisation
[17:24:04] <thiago> lots of people (including me) are doing that and assuming that they're still in 5.8
[17:24:15] <thiago> we need a specific point in time when that won't be the case any more
[17:24:24] <thiago> it can't be "any moment now"
[17:26:20] <thiago> can we have a more definite date?
[17:26:26] <jaheikki3> Hmm, i somehow disagree but understand your point
[17:28:05] <thiago> shall we say next Monday?
[17:28:18] <thiago> anything that is in dev after next Monday risks not being in 5.8
[17:28:38] <jaheikki3> thiago: That is OK for me.
[17:28:54] <thiago> ok
[17:29:40] <lars> ok, that should give us enough time for the configuration changes as well.
[17:29:58] <jaheikki3> great
[17:30:03] <lars> but let's not delay further.
[17:30:07] <jaheikki3> agree
[17:30:30] <jaheikki3> it is next monday, lets make sure all needed is ready at that point
[17:31:00] <jaheikki3> Ok, it is all about 5.8 at this time
[17:31:13] <lars> 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] <jaheikki3> lars: Yes, I'll do that
[17:31:46] <lars> jaheikki3: thanks
[17:31:57] <jaheikki3> Then Qt 5.6.1 and Qt 5.7.1 status
[17:32:08] <lars> jaheikki3: especially no changes to public or internal APIs for this one week
[17:32:36] <lars> to avoid further qt5.git issues
[17:32:40] <jaheikki3> Yeah
[17:33:27] <jaheikki3> - Unfortunately no real progress with Qt 5.6.2 or Qt 5.7.1 releases since last meeting :(
[17:33:50] <jaheikki3> We tried to create first snapshots but noticed some binaries were missing
[17:34:41] <jaheikki3> 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] <jaheikki3> Next tries during next night, hoping those will succeed to be able to create the snapshots for testing
[17:36:32] <thiago> what's our target
[17:36:35] <thiago> release ASAP?
[17:36:49] <jaheikki3> thiago: I would say yes
[17:36:53] <thiago> ok
[17:36:57] <thiago> that's good info
[17:37:10] <thiago> I'd been prioritising 5.8 stuff, but I need to get back to fixing 5.6 now
[17:37:13] <jaheikki3> But we need to get first snapshot for testing to see where we are
[17:37:34] <thiago> true
[17:38:53] <jaheikki3> I think it was all about 5.6.2 & 5.7.1
[17:39:19] <jaheikki3> Is there something else at this time or should we end the meeting now & have new next tue?
[17:40:18] <fkleint> are we planning a 5.7.2?
[17:40:31] <fkleint> that is, when can we declare 5.7 dead?
[17:41:21] <fkleint> very ideally, branch n-1 should be closed before n is branched as long as there is a LTS..
[17:41:43] <jaheikki3> fkleint: we need to agree that later
[17:42:05] <thiago> we should release 5.7.x until we have 5.8.0
[17:42:08] <thiago> then we can stop
[17:42:33] <fkleint> hm
[17:43:47] <jaheikki3> lets check that after we have released 5.7.1
[17:44:03] <fkleint> m,ok
[17:44:59] <jaheikki3> Ok, I need to go now. so let's end this meeting now. thank & bye
[17:45:06] <fkleint> 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://qt.io/>

[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/>
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]<http://www.facebook.com/Qt>     [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] <http://www.twitter.com/qtproject>       [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] <https://www.linkedin.com/company/the-qt-company/>      [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] <https://plus.google.com/104580575722059274792>       [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] <https://www.youtube.com/QtStudios>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20160817/761820b9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutlookEmoji-☹.png
Type: image/png
Size: 506 bytes
Desc: OutlookEmoji-☹.png
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20160817/761820b9/attachment.png>