[Releasing] Meeting minutes: Qt 5.1.1 release team meeting 12.08.2013

Mon Aug 12 17:03:12 CEST 2013

Hi,

Meeting minutes from Qt 5.1 release team meeting 12.08.2013:

-        5.1.1 installers are in good condition

o   New installers has been available almost daily

-        5.1.1 error condition in pretty good shape

o   There is quite many open P1 issues but all P0's are fixed

è Current snapshot will be used as a release candidate

o   Rafal will sent an email to the community to get RC tested

-        Target is to release Qt 5.1.1 during next week if nothing serious found during testing

Next meeting: Monday 19.08.2013 16:00-17:00 CET

Br,

Jani

Irc log below:
[17:02:02] <jaheikki3> akseli: iieklund: kkoehne_: sahumada: thiago: fkleint: ZapB_: tronical: ramotyka_: wolfgang-b: vladimirM: ping
[17:02:08] <sahumada> jaheikki3: pong
[17:02:17] <wolfgang-b> jaheikki3, pong
[17:02:20] <thiago> jaheikki3: pong
[17:02:34] <ramotyka__> jaheikki3: pong
[17:02:47] <vladimirM> pong
[17:02:59] <kkoehne_> jaheikki3: pong
[17:03:42] <jaheikki3> Time to start Qt 5.1.1 release meeting
[17:04:24] <jaheikki3> On agenda today:
[17:04:35] <jaheikki3> 5.1.1 Installer status
[17:04:35] <jaheikki3> 5.1.1 Error status
[17:04:35] <jaheikki3> 5.1.1 Release
[17:04:35] <jaheikki3> Next meeting
[17:04:42] <jaheikki3> Any additional items to agenda?
[17:06:50] <jaheikki3> OK, let's start from installer status: sahumada^
[17:07:12] <sahumada> jaheikki3: no problems so far .. we've been having packages almost every day now
[17:07:20] <sahumada> jaheikki3: qt5#release is up-to-date as well
[17:08:40] <sahumada> that's pretty much the status
[17:08:47] <jaheikki3> sahumada: I noticed that. Great work.
[17:10:01] <jaheikki3> OK, let's continue with error status then. At the moment there is only 2 open issues in 5.1.1 metatask
[17:10:15] <jaheikki3> https://bugreports.qt-project.org/browse/QTBUG-32183
[17:10:23] <jaheikki3> QTBUG-32808: Add missing changes files (qtbase, qtdeclarative, qtmultimedia)
[17:10:33] <jaheikki3> QTBUG-32241: Severe Flickering Regression on transitioning from Qt 5.02 to Qt 5.1
[17:11:21] <jaheikki3> Does someone know details about those? I haven't had time to clarify those yet...
[17:11:59] <jaheikki3> At least that change files issue doesn't have responsible person at all?
[17:12:26] <sahumada> it should be module's maintainers .. so no one single person
[17:12:55] <jaheikki3> sahumada: Do you know if someone has done something related to it?
[17:13:17] <sahumada> jaheikki3: I dont think anybody has done anything related to it
[17:13:44] <jaheikki3> Is it "only" for those three modules?
[17:14:20] <sahumada> jaheikki3: I think so
[17:15:41] -*- thiago counts a total of 0 uses of [ChangeLog] in the release branches now
[17:16:31] <jaheikki3> I'll try to contact maintainers directly to get that one fixed
[17:17:12] <jaheikki3> And I have already asked status from Gunnar related to that another one. Hoping we can get those fixed soon.
[17:18:04] <sahumada> what about QTBUG-32825 and QTBUG-32826 .. they were "nominated" as blockers
[17:18:26] <sahumada> QTBUG-32221 as well
[17:20:09] <jaheikki3> sahumada: Where/who nominated those as a blocker?
[17:20:36] <ramotyka__> Two of them are P2s
[17:20:42] <sahumada> jaheikki3: See comments for QTBUG-32183 / Chris Meyer
[17:21:20] <sahumada> well .. if they are P2 then nm
[17:22:37] <jaheikki3> I'll discuss with Chris about those but I don't see P2 blocking the release
[17:22:55] <ramotyka__> We have 54 other P1s against 5.1.x which could be added also.
[17:23:22] <ramotyka__> ...not mentioning 5.0.x.
[17:24:02] <thiago> we still have P1s with "fixed for" 5.0.x?
[17:24:06] <jaheikki3> ramotyka__: that was my next question: Does anyone know some issue which isn't listed/linked to that metabug but which is blocking the release?
[17:24:57] <jaheikki3> thiago:I think ramotyka__ is referring p1 issues which are open and reported against 5.0.x
[17:25:09] <ramotyka__> jaheikki3: If we take the common Qt understanding of P1 there is 54 unresolved P1s reported against 5.1.x
[17:25:48] <ramotyka__> ... and around 30 P1s reported for 5.0.x still not resolved.
[17:26:57] <jaheikki3> I notice that. But in reality we cannot fix those all before 5.1.1 release :(
[17:27:15] <thiago> any P0s?
[17:27:28] <thiago> since we have fixed P0s, I say we need to release ASAP
[17:27:36] <ramotyka__> Yes. I mentioned P1s because we were discussing P2s as blocking issues.
[17:28:25] <jaheikki3> thiago: No p0
[17:28:26] <ramotyka__> I cannot see any P0 reported against 5.x.x.
[17:29:36] <jaheikki3> We started to discuss about releasing so let's continue with next topic which is 5.1.1 Release
[17:30:13] <jaheikki3> I agree with thiago that if there isn't blocking issues we should do the release pretty soon
[17:31:39] <thiago> in theory those p1s are blocking
[17:32:07] <thiago> but I'm going to say we have enough fixes including for p0s
[17:32:09] <thiago> so release ASAP
[17:33:01] <jaheikki3> Can we even call next build as release canditate and ask community to test it
[17:33:21] -*- thiago agrees
[17:33:47] <jaheikki3> And if no blocking issues found then release it as a final 22.8 as planned before summer vacations?
[17:34:28] <jaheikki3> 10 days should be enough for community testing
[17:34:32] <jaheikki3> in my opinion
[17:34:54] <thiago> agreed
[17:34:59] <ramotyka__> But let's test it first. Jani, Should we wait for tomorrow's packages and invite the Qt Community or ask them to test what we have today?
[17:36:51] <jaheikki3> In my opinion we use tomorrows packages, it is easiest that way
[17:37:11] <ramotyka__> sahumada: Do we get many changes every day?   Why not to call the last packages 'RC' and ask for testing today?
[17:38:10] <jaheikki3> sahumada: ramotyka__: That is OK for me as well
[17:38:18] <sahumada> ramotyka__: no we dont .. maybe one or two a dat
[17:38:19] <sahumada> day*
[17:39:44] <jaheikki3> OK, let's call currect packages as RC and rafal can ask community to test those
[17:42:01] <jaheikki3> Is there anything else of should we decide next meeting?
[17:42:58] <thiago> like?
[17:43:43] <jaheikki3> thiago: I don't know, something you want to discuss...
[17:44:37] <ramotyka__> Like 'missing examples in qt creator'
[17:45:21] <jaheikki3> ramotyka__:?
[17:45:35] <ramotyka__> It was an example only  ;)
[17:45:45] <jaheikki3> OK ;)
[17:45:52] <thiago> nothing from me then
[17:46:20] <ramotyka__> nothing
[17:46:29] <jaheikki3> I think we don't need meeting on next week if we are testing RC
[17:47:42] <jaheikki3> SOrry, maybe we need because it nothing serious found we will do release during that week
[17:48:01] <jaheikki3> SO next meeting 19.8 in that same time, OK?
[17:48:19] <ramotyka__> ok
[17:49:03] <thiago> ok
[17:49:38] <jaheikki3> OK, let's close this meeting now. Thank and have a nice week!
[17:49:48] <ramotyka__> thanks, you too!
[17:49:56] <jaheikki3> bye
[17:50:42] <sahumada> bye
[17:50:45] <thiago> see ya

------------------------------------------------------------------
Jani Heikkinen
Release Manager

Digia Plc
Elektroniikkatie 10, FI 90590 Oulu Finland
Email: jani.heikkinen at digia.com<mailto:jani.heikkinen at digia.com>
Mobile: +358-504-873-735
Visit us at: www.digia.com<http://www.digia.com/>
| Blog<http://blog.digia.com/> | Twitter<https://twitter.com/digiaonline> | LinkedIn<http://www.linkedin.com/company/5119> | YouTube<http://www.youtube.com/digiaonline> | Facebook<http://www.facebook.com/digiaonline> |
------------------------------------------------------------------
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. Digia Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message.
------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20130812/eb11c204/attachment.html>