[Releasing] Meeting minutes: Qt 5.2 release team meeting 25.11.2013

[Salovaara Akseli]

Meeting minutes from Qt 5.2.0 release team meeting 25.11.2013:

Qt 5.2 RC1 status:
- Connection problems on build system and broken submodule update during weekend
- Items currently expected for RC1 are either merged or fix integrating
- New packages (available during Tuesday) should have those fixes available and enable then RC1 later this week  (Update 26.11.: http://lists.qt-project.org/pipermail/development/2013-November/014288.html )
- Some recent change broke the qml2puppet builds on Linux. Fix available but doesn't require submodule update.
- https://codereview.qt-project.org/#change,72149 not a blocker for RC1
- https://codereview.qt-project.org/#change,72023 not a blocker for RC1 or final
Next meeting: Monday 2.12. 16:00 CET

Irc log below:
(5:00:45 PM) akseli: iieklund: kkoehne: sahumada: thiago: fkleint: ZapB_: tronical: wolfgang-b: vladimirM: aholza: peter-h: mapaaso: ankokko ping
(5:00:51 PM) iieklund: akseli: pong
(5:00:52 PM) wolfgang-b: akseli, pong
(5:00:58 PM) thiago [~thiago at kde/thiago] entered the room.
(5:00:59 PM) mapaaso: akseli:pong
(5:01:02 PM) ankokko: akseli: pong
(5:01:15 PM) thiago: akseli: pong
(5:02:34 PM) fkleint: akseli: pong
(5:02:59 PM) akseli: Time to start Qt 5.2 release team meeting
(5:03:04 PM) akseli: jaheikki3 is on sick leave so I'll be covering today
(5:03:19 PM) akseli: Agenda for the meeting
(5:03:23 PM) akseli: Qt 5.2 RC1 status
(5:03:27 PM) akseli: http://qt-project.org/wiki/Building_Qt_5_from_Git & version info
(5:03:31 PM) akseli: Next meeting
(5:03:43 PM) akseli: Any additional items anyone?
(5:04:16 PM) peter-h: akseli: pong
(5:04:17 PM) wolfgang-b: Maybe it is part of the RC1 status, but I want to have decision regarding this patch https://codereview.qt-project.org/#change,72023
(5:05:36 PM) akseli: ok, lets include that. feel free to raise additional topics at the end of the meeting
(5:05:41 PM) akseli: Starting from Qt 5.2 RC1 status
(5:05:56 PM) akseli: Unfortunately we have had both connection problems on build system and broken submodule update (fixed yesterday evening) during weekend so there is no packages available. 
(5:06:16 PM) akseli: We were able to get missing iOS installers at the end of the last week before those problems occured.
(5:06:28 PM) anshaw_ left the room (quit: Ping timeout: 264 seconds).
(5:06:38 PM) akseli: All items from Finalizing Qt5.2 RC1 -list (http://lists.qt-project.org/pipermail/releasing/2013-November/001508.html) are now either already merged or integrating.
(5:07:10 PM) akseli: meaning original email and ecluding later raised https://codereview.qt-project.org/#change,72023
(5:07:50 PM) akseli: Also all items from "Issues to be fixed before Qt5.2 RC1 release" (https://bugreports.qt-project.org/browse/QTBUG-33863)
(5:08:55 PM) akseli: are either merged or integrating. Due to connection or submodule update problem packages are not available so we are not able to verify all yet
(5:09:23 PM) thiago: when should we see that?
(5:09:26 PM) akseli: therefore QTBUG-33863 is not quite up to date also
(5:10:04 PM) akseli: we are aiming to have submodule update & builds during the night so tomorrow is the day for heavy testing
(5:11:27 PM) thiago: great
(5:12:19 PM) akseli: did i miss something, iieklund^ mapaaso^ ankokko^
(5:12:39 PM) ankokko: akseli: just noticed this: https://codereview.qt-project.org/#change,72149
(5:12:40 PM) iieklund: akseli: qml2puppet build issue on linux, kakoehne?
(5:13:01 PM) iieklund: kkoehne ^
(5:13:27 PM) iieklund: some recent change in qmake(?) broke the qml2puppet builds on linux, kai/eike was looking at this today
(5:16:21 PM) akseli: proposing https://codereview.qt-project.org/#change,72149 for RC1 to be known issue and fix for final
(5:17:11 PM) akseli: if that gets in & integrated earlier then fine but i doubt it will be on time on nightly build
(5:17:37 PM) thiago: I agree
(5:17:38 PM) thiago: stage it
(5:17:41 PM) wolfgang-b: Ok, so what about the mentioned configure patch https://codereview.qt-project.org/#change,72023? Do we want it or is just the failure of the user if configure fails without any messages?
(5:17:46 PM) thiago: it'll be there for the final
(5:18:10 PM) thiago: it seems cosmetic to me
(5:18:21 PM) thiago: people shouldn't have scripts that pass bad arguments
(5:18:44 PM) wolfgang-b: forget about the scripts, what if someone passes them manually?
(5:18:46 PM) thiago: also, there's some dispute whether configure should complain about bad arguments or if it should just chug along with what it did understand
(5:19:13 PM) thiago: I'd say it's a good fix, but not enough to delay the RC
(5:19:14 PM) wolfgang-b: both would be fine, currently it just fails without anything
(5:19:16 PM) thiago: or the final, for that matter
(5:20:15 PM) thiago: I'd say stage it, but don't hold back package building
(5:20:26 PM) wolfgang-b: fine with me
(5:20:39 PM) akseli: thiago: wolfgang-b: ok, thank you
(5:22:03 PM) akseli: about qml2puppet. i think kakoehne & eike had some progress with that. of course have to be fixed in order to get linux packages but it doesn affect to submodule updates etc
(5:22:46 PM) akseli: so with above mentioned fixes & decisions we will release RC1 later this week
(5:23:01 PM) akseli: if of course no new blockers are found on testing
(5:23:03 PM) akseli: does all agree?
(5:23:28 PM) iieklund: yes
(5:24:01 PM) fkleint: yup
(5:24:08 PM) ankokko: yes
(5:24:09 PM) wolfgang-b: yes
(5:24:14 PM) ZapB: yes
(5:24:15 PM) mapaaso: yes
(5:25:26 PM) akseli: ok, thank you .. then next item 
(5:25:39 PM) akseli: http://qt-project.org/wiki/Building_Qt_5_from_Git & version info
(5:26:30 PM) fkleint: How does that relate to releases?
(5:27:46 PM) akseli: there have been some discussio about different minimum versions (e.g. python, mysql etc) which are supported on Qt releases
(5:28:23 PM) thiago: are we having build issues?
(5:28:31 PM) akseli: or which all configurations & versions are currently supported by default with different Qt versins
(5:28:49 PM) akseli: is that sort of information available somewhere at the moment?
(5:29:08 PM) akseli: or should it be documented, if not that wiki page, then similar 
(5:29:09 PM) akseli: ?
(5:30:08 PM) fkleint: it should be documented *somewhere* , but that wiki page is only for build tools, so , mysql etc is a different issue
(5:30:16 PM) akseli: thiago: no build issues 
(5:31:02 PM) fkleint: that information is currently spread all over the place, fex for XCB, there is a README ins the source code...
(5:31:27 PM) fkleint: not sure whether there should be a central page and how to maintain it
(5:32:51 PM) ankokko:  https://codereview.qt-project.org/#change,72023 -> missing approval
(5:32:59 PM) ankokko: https://codereview.qt-project.org/#change,72149 -> staged
(5:33:51 PM) wolfgang-b: ankokko, I know, I hoped thiago or someone else will approve it, I cannot
(5:35:29 PM) thiago: oh
(5:35:50 PM) thiago: done now
(5:35:56 PM) wolfgang-b: thiago, thx
(5:36:09 PM) ankokko: ok, thanks
(5:36:16 PM) akseli: ankokko: thiago: thank you
(5:36:17 PM) akseli: ok, maybe that version info is something which should be handled on mailing list
(5:36:52 PM) akseli: and i agree that building from git wiki page is not correct place to have all that information
(5:37:42 PM) akseli: but any other items\topics anyone? besides next meeting
(5:40:04 PM) akseli: if nothing else then is next Monday 16 CET alright for all?
(5:40:21 PM) fkleint: Yup, I guess,.in the hopes of having an RC...
(5:41:31 PM) akseli: ok, thank you all participating the meeting