[Releasing] Meeting minutes from Qt Release Team meeting 19.03.2019

[Jani Heikkinen]

Meeting minutes from Qt Release Team meeting 19th March 2019

Qt 5.13:
- Beta1 released finally today
- Target is to get beta2 out within two weeks
- API review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-73484
   * Please finalize ongoing ones as soon as possible
  
Qt 5.9:
- Qt 5.9.7 was released at the end of October so it is time to start preparations for Qt 5.9.8
   * ~ 80 changes in '5.9' since Qt 5.9.7 release
   * Branching from '5.9' to '5.9.8' will start during this week
   * Target is to create snapshot for testing as soon as possible & get Qt 5.9.8 release out ~ two weeks
- We will most probably do Qt 5.9.9 release autumn 2019 and most probably it will be the last release for Qt 5.9 series

Qt 5.12.3
- Preparation for the release to be started, there is already more than 200 changes in '5.12' since 5.12.2 release!
   * Branching from '5.12' to '5.12.3' to be started at the beginning of next week. That way we should be able to get the release out before Easter. 

br,
Jani Heikkinen
Release Manager

rc log below:
[17:00:06] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping
[17:00:14] <thiago> jaheikki3: pong
[17:00:29] <frkleint> jaheikki3: ping
[17:00:33] <lars> jaheikki3: pong
[17:01:07] <jaheikki3> Time to start qt release team meeting
[17:01:12] <jaheikki3> On agenda today:
[17:01:26] <jaheikki3> Qt 5.13 status
[17:01:35] <jaheikki3> Qt 5.9.8 plan
[17:01:39] <jaheikki3> Qt 5.12.3 plan
[17:01:48] <jaheikki3> Any additional item to the agenda?
[17:03:17] <jaheikki3> Let's start from 5.13 status
[17:03:27] <jaheikki3> Beta1 released finally today
[17:03:39] <jaheikki3> Hoping all start testing now
[17:03:51] <jaheikki3> Target is to get beta2 out within two weeks
[17:04:06] <jaheikki3> API review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-73484
[17:04:07] <qt_gerrit> jaheikki3: API change review for 5.13 vs v5.12.0 - https://bugreports.qt.io/browse/QTBUG-73484 (Reported)
[17:04:15] <jaheikki3> Please finalize ongoing ones as soon as possible
[17:04:42] <jaheikki3> That's pretty much all about 5.13 at this time. Any comments or questons?
[17:05:41] <vladimir-m_> missed the most of it joining late...
[17:06:05] <thiago> there wasn't much
[17:06:10] <thiago> 08:04 < jaheikki3> API review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-73484
[17:06:11] <qt_gerrit> thiago: API change review for 5.13 vs v5.12.0 - https://bugreports.qt.io/browse/QTBUG-73484 (Reported)
[17:06:16] <thiago> that's basically it
[17:06:29] <jaheikki3> Yeah, true
[17:06:48] <jaheikki3> Then Qt 5.9.8 plan
[17:07:47] <jaheikki3> There seems to be ~ 80 changes in '5.9' since Qt 5.9.7 release which was done at the end of October
[17:08:10] <jaheikki3> So I think it is time to start preparations for the release
[17:08:27] <thiago> ok, not much, but good idea
[17:08:58] <jaheikki3> yes, few changes should make the release pretty easy
[17:08:58] <thiago> we're coming up on the two-year anniversary for 5.9
[17:09:05] <thiago> how long do we expect to continuing to release?
[17:10:02] <jaheikki3> I haven't thought that yet but because amounth of changes are decreasing there shoudn't be that many releases from '5.9' anymore
[17:10:30] <thiago> I agree
[17:10:38] <thiago> but we should make an annoucement
[17:10:40] <jaheikki3> Let's do 5.9.8 now & see in autumn if we need still more
[17:10:44] <lars> jaheikki3: maybe one or two more? unless we need something because of security issues...
[17:10:48] <thiago> the 5.9.0 release was May 22, 2017
[17:11:03] <thiago> security releases are different, we can always make them
[17:11:07] <thiago> for any branch
[17:11:34] <lars> thiago: sure, but they are a release nevertheless :)
[17:11:42] <thiago> I'd say we should say 5.9.9 is likely, but that it is likely the last
[17:11:55] <lars> agree
[17:12:10] <jaheikki3> agree
[17:12:39] <carewolf> we will need some time to backport security fixes in qtwebengine
[17:12:49] <carewolf> when would you want to release 5.9.8?
[17:13:57] <jaheikki3> carewolf: there will be. let's start branching during this week & do the release within coming weeks. Preferrably as early as possible but on the other hand we aren't that hurry
[17:14:07] <thiago> I think we can invert this: how long do you need?
[17:14:20] <thiago> there's nothing pressing in 5.9.8, so we can simply release when you're ready
[17:14:44] <carewolf> probably a week or two, it can be done by two people in a couple of days, but we are quite bussy
[17:14:54] <carewolf> ok
[17:15:09] <jaheikki3> carewolf: it will take that to get the changes files in as well :D
[17:15:19] <carewolf> great :)
[17:16:33] <jaheikki3> Ok, that's all about 5.9.8. Ony other comments or questions?
[17:18:03] <jaheikki3> Ok, then 5.12.3 plan
[17:18:37] <jaheikki3> It is about a month from branching '5.12.2' from '5.12'
[17:18:57] <jaheikki3> And there seems to be more than 200 changes in '5.12' since Qt 5.12.2 release
[17:19:24] <jaheikki3> So i think it is also time to start preparations for Qt 5.12.3 release
[17:19:39] <vladimir-m_> plus some bugreports which are not attended...
[17:20:32] <jaheikki3> I was planning that we should try to get 5.12.3 out before easter so we need to start branching from '5.12' to '5.12.3' at the beginning of next week
[17:20:35] <thiago> I can't believe I'm saying this, but didn't we just release 5.12.2?
[17:20:43] <thiago> I upgraded it during the weekend in my distro
[17:21:00] <jaheikki3> thiago: yes we did but finalizing it took quite long
[17:21:14] <jaheikki3> vladimir-m_: any special ones on your mind?
[17:21:35] <vladimir-m_> my high, or better, lowlight is that Qt 3D eats CPU with an empty QML scene. If the scene is not empty, than the CPU load is even higher
[17:21:54] <thiago> regression?
[17:22:09] <vladimir-m_> according our experience, this affects Qt 3D Studio runtime
[17:22:25] <jaheikki3> vladimir-m_: is there a bug ID for that?
[17:23:02] <vladimir-m_> jaheikki3: yes... wait a second...
[17:24:58] <vladimir-m_> https://bugreports.qt.io/browse/QTBUG-74103
[17:24:58] <qt_gerrit> vladimir-m_: An empty Scene3D causes a high CPU load - https://bugreports.qt.io/browse/QTBUG-74103 (Reported)
[17:25:15] <vladimir-m_> he! I was faster! :-)
[17:25:51] <frkleint> Mesa..well
[17:26:35] <jaheikki3> vladimir-m_: It seems this isn't a regression at least in 5.12.2, right?
[17:27:57] <vladimir-m_> anyways, I had a chat with James Turner at Embeddd World. He asked for max details, since it is a known problem which appraently pops up regularily
[17:28:58] <jaheikki3> Ok. Hoping they can find a fix soon. Let's see if it will be in 5.12.3 or not; 5.12.4 will coming soon anyway :D
[17:29:00] <vladimir-m_> he said it is usually some small timing mismatches which run out of sync again and again
[17:29:57] <vladimir-m_> My hope is not that large, since there is no attention to this problem, at least from my perspective...
[17:30:35] <jaheikki3> let's see...
[17:30:59] <jaheikki3> But it was all about 5.12.3 at this time. Any more comment or questions?
[17:31:17] <vladimir-m_> I will go and set fix version to 5.12.3 ... let's see...
[17:32:24] <thiago> is it a regression from an earlier version?
[17:33:18] <jaheikki3> thiago: according to my understanding no. At least it seems 5.12.1 was already affecting
[17:33:25] <jaheikki3> vladimir-m_: ^^
[17:34:23] <thiago> just checking
[17:35:46] <jaheikki3> Ok, it is now in 5.12.3 blocker list but let's get back to it if it is still open at the time when we are otherwise ready for the release
[17:36:13] <jaheikki3>  let's end this meeting now & have next one tue 26th March as planned
[17:36:25] <jaheikki3> Thanks for your participation. Bye!
[17:39:18] <thiago> thanks
[17:39:19] <thiago> bye