[Releasing] Meeting minutes: Qt release team meeting 12.05.2015

[Heikkinen Jani]

Meeting minutes from Qt Release Team meeting 12th May 2015

Qt 5.5 Beta status
- New snapshot under testing, no new blockers reported so far
- All known blockers fixed now, re-building ongoing
- Target is to have final beta packages for testing tomorrow morning & release beta during this week (if no more blockers found)

Qt 5.4.2 status
- "rc" packages under testing, no new blockers reported so far
- QTBUG-45755 needs still an additional change: https://codereview.qt-project.org/#/c/112053/ (that should be the last one needed for Qt 5.4.2)
- When that change in qt5.git we will create final Qt5.4.2 packages for final testing
- Target is to get Qt5.4.2 out during next week

Qt 4.8.7 status:
- Qt 4.8.7 release candidate 2 available ( http://lists.qt-project.org/pipermail/development/2015-May/021312.html )
- No release blockers informed from rc1 or rc2 via mailing lists
- Qt 4.8.7 release will be available when final installers are build and signed
* Binary installer for msvc2013 will be offered for Qt4.8.7 if ready early enough but we won't the qt4.8.7 release because of that

Qt5.6 initial plan:
- Earlier we tried to execute our releases according to schedule skeleton in https://wiki.qt.io/Qt5Releasing
- We have been late always (with 5.1, 5.2, 5.3 & 5.4), that's why plan for 5.6 is now done based on actual schedules earlier
* Plan will be updated after each release phase (if needed)
- Initial plan for Qt5.6 release (updated also in https://wiki.qt.io/Qt-5.6-release )
* Feature Freeze 10th August 2015 		
* Branch 5.6 from dev 10th August 2015 		
* Alpha Release 8th Sep 2015 		
* Beta Release 13th October 2015 		
* String freeze 31st October 2015 		
* Branch 5.6.0 from 5.6 9th November 		
* Release Candidate 24th November 2015 		
* Final Release 8th December 2015
- In addition to this plan we need to get all new modules in qt5.git before end of June to be able to keep the FF
* FF is during holiday period/immediately after it & we cannot get new modules in during holidays -> we need to get new modules in early enough

Next meeting Tue 19.5.2015 16:00 CET

Br,
Jani

Irc log below:
[17:00:38] <jaheikki3> akseli: iieklund: kkoehne: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche_ ping
[17:01:09] <fkleint> jaheikki3: ping
[17:01:10] <akseli> jaheikki3: pong
[17:01:46] <kkoehne> jaheikki3: pong
[17:02:51] <jaheikki3> Time to start qt release team meeting
[17:03:00] <jaheikki3> On agenda today:
[17:03:06] <jaheikki3> Qt5.5 beta status
[17:03:12] <jaheikki3> Qt5.4.2 Status
[17:03:18] <jaheikki3> Qt 4.8.7 status
[17:03:29] <jaheikki3> Qt 5.6 initial schedule
[17:03:40] <jaheikki3> Any additional items to the agenda?
[17:03:57] <carewolf> pong
[17:05:13] <jaheikki3> Lets start from Qt 5.5 Beta status
[17:05:50] <jaheikki3> - New snapshot under testing, no new blockers reported so far
[17:06:12] <jaheikki3> All known blockers fixed now, re-building ongoing
[17:06:23] <fkleint> except the installaer process blocking , but ok...
[17:07:05] <jaheikki3> fkleint: I thought that was fixed in IFW 2.0?
[17:07:12] <fkleint> dunno
[17:07:35] <fkleint> if that takes effect in the  packages, all should be fine..
[17:07:55] <jaheikki3> fkleint: I think kakoehne said so. We rebuild IFW & coming packages should have newest version there
[17:07:59] <fkleint> oki
[17:08:52] <jaheikki3> Hoping builds goes ok & we could have final beta packages for testing tomorrow morning
[17:09:16] <jaheikki3> & if no new blockers found we are planning to release beta still during this week
[17:09:33] <jaheikki3> Any comments/questions?
[17:11:52] <jaheikki3> Then Qt 5.4.2 status
[17:12:04] <jaheikki3> "rc" packages under testing
[17:12:17] <jaheikki3> no new blockers reported so far
[17:12:53] <jaheikki3> https://bugreports.qt.io/browse/QTBUG-45755 needs still an additional change: https://codereview.qt-project.org/#/c/112053/
[17:13:16] <jaheikki3> That should be the last one needed for Qt 5.4.2
[17:13:33] <fkleint> ohh crap..tst_bic again involved
[17:13:41] <jaheikki3> Yeah :(
[17:14:27] <jaheikki3> When that change in qt5.git we will create final Qt5.4.2 packages
[17:14:50] <jaheikki3> Then final testing & we should be ready for the release
[17:15:03] <jaheikki3> Hoping we could get 5.4.2 out during next week
[17:15:13] <jaheikki3> Any comments / questions?
[17:16:51] <jaheikki3> Then Qt 4.8.7 status, akseli:
[17:17:29] <akseli> Qt 4.8.7 release candidate 2 available ( http://lists.qt-project.org/pipermail/development/2015-May/021312.html )
[17:17:35] <akseli> No release blockers informed from rc1 or rc2 via mailing lists
[17:17:42] <akseli> Qt 4.8.7 release will be available when final installers are build and signed
[17:17:51] <akseli> Any comments / questions?
[17:19:01] <fkleint> carewolf: akseli is having issues with WebKit/VS2013 in 4.,8.7 I heard?
[17:19:18] <carewolf> fkleint: I haven't heard anything
[17:19:23] <fkleint> ;-)
[17:19:34] <fkleint> Yep , I also think I got that to compile
[17:19:54] <fkleint> akseli: ^^^^^^^^^^ Was that blocking a 4.8.7 / VS2013 package?
[17:20:07] <akseli> i just had time to try one build machine .. another build instance with vs2013 ongoing so lets see 
[17:20:14] <akseli> i suspect it's environment issue
[17:21:19] <akseli> hopefully vs2013 & webkit compiles properly on the other machine
[17:21:24] <jaheikki3> I propose that we will offer vs2013 package for Qt4.8.7 if ready early enough but not block the qt4.8.7 release because of that
[17:21:51] <fkleint> yep, and maybe provide package later..doesn't really matter
[17:21:59] <fkleint> but it is clearly nice to  have
[17:22:03] <akseli> sounds like a plan 
[17:22:43] <jaheikki3> Ok, then qt5.6 initial plan:
[17:23:41] <jaheikki3> We have trying to execute our releases according to plan skeleton in https://wiki.qt.io/Qt5Releasing
[17:24:48] <jaheikki3> We have failed to execute that plan every time & for 5.6 I made some analysis about times taken between each release phase
[17:26:19] <jaheikki3> it seems we need 4 weeks between FF-> Alpha, 5 weeks between Alpha-> Beta, 6 weeks between beta -> RC and 2 weeks between RC-> Final
[17:26:48] <jaheikki3> That is calculated from 5.1, 5.2, 5.3 & 5.4 releases
[17:27:05] <jaheikki3> So that's why initial plan for Qt5.6 is:
[17:27:38] <jaheikki3> Feature Freeze 10th August 2015 
[17:27:38] <jaheikki3> Branch 5.6 from dev 10th August 2015 
[17:27:38] <jaheikki3> Alpha Release 8th Sep 2015 
[17:27:38] <jaheikki3> Beta Release 13th October 2015 
[17:27:38] <jaheikki3> String freeze 31st October 2015 
[17:27:38] <jaheikki3> Branch 5.6.0 from 5.6 9th November 
[17:27:38] <jaheikki3> Release Candidate 24th November 2015 
[17:27:38] <jaheikki3> Final Release 8th December 2015
[17:28:42] <jaheikki3> And in addition to this we need to get all new modules in qt5.git at the end of June
[17:28:48] <fkleint> [way too rushed - FF in the middle of holidays] but that is just my personal opinion
[17:29:34] <jaheikki3> fkleint: Well, we in Finland should be back from holidays then
[17:29:35] <carewolf> do we really need that long for alpha? I thought that was just a sources release
[17:29:58] <jaheikki3> carewolf: that has been necessary earlier
[17:30:30] <jaheikki3> carewolf: So let's no reserve that time for it. But of course we will release Alpha earlier if possible
[17:31:01] <jaheikki3> We will update the plan after each phase if needed
[17:32:20] <jaheikki3> Hoping we can make 5.6 within shorter time than that. But I don't want to make too tight plan at this time: It is better to do realistic plan than be always late...
[17:33:46] <jaheikki3> Any other comments?
[17:36:04] <jaheikki3> Ok, I think it was all at this time. Ok to have new meeting next Tue at this same time?
[17:37:14] <akseli> +1
[17:37:24] <fkleint> +1
[17:38:56] <jaheikki3> Lets end this meeting now & have new one next Tuesday. Thanks & bye!
[17:39:17] <akseli> bye
[17:39:23] <fkleint> bye