<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Qt 5.0.1 release team has continued work as Qt 5.0.2 release team with few additional members. Release team for Qt 5.0.2 at the moment: Ahumada Sergio, Eklund Iikka, Harmer Sean, Hausmann Simon, Kleint Friedemann,
 Koehne Kai, Macieira Thiago, Motyka Rafal, Salovaara Akseli. If someone else is willing to participate to Qt 5.0.2 release team work please send me an email.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">There will be separate call for Qt 5.1 release team later.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Meeting minutes from Qt 5.0.2 release team meeting 05.03.2013<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- Two new reference installers available  for Qt 5.0.2: MSVC2010 (32bit) OpenGL and MSVC2012 64bit / Win8. Note: OpenGL packages doesn't have Webkit2 support.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- Content of current installer packages (<a href="http://releases.qt-project.org/digia/5.0.2/">http://releases.qt-project.org/digia/5.0.2/</a>) is not yet up to date as things have been lately blocked in CI.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- Creator 2.7.0 to be included into Qt 5.0.2 packages (decision depends on 2.7 RC release schedule).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- No changes for MinGW tool chain even performance issues have been reported. Possible tool chain changes will be handled on Qt 5.1.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- Possibility for decreasing ICU library size (QTBUG-29828) is investigated but aimed mainly for Qt 5.1.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- Autotests will stay as part of src packages.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">- Next meeting: Tuesday 12.03.2013 09:00 CET.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">The irc log below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Br,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Akseli<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#204A87"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#204A87">(9:02:37 AM) </span>
<b><span style="color:#204A87">akseli: </span></b>iieklund: kkoehne: ramotyka: tronical: thiago: ZapB: ping<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:02:43 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: pong<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:02:45 AM) </span><b><span style="color:#AF7F00">iieklund:
</span></b>akseli: pong<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:02:45 AM) </span><b><span style="color:#AF7F00">thiago:
</span></b>akseli: pong<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:02:50 AM) </span><b><span style="color:#AF7F00">ZapB:
</span></b>akseli: pong<br>
<span style="font-size:10.0pt">(9:03:07 AM) </span><b>fkleint [<i>~fkleint@62.220.2.194</i>] entered the room.</b><br>
<span style="font-size:10.0pt;color:#204A87">(9:03:43 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Time to start Qt 5.0.2 release meeeting<br>
<span style="font-size:10.0pt;color:#204A87">(9:03:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>I'm proposing following agenda:<br>
<span style="font-size:10.0pt;color:#204A87">(9:03:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Installer status<br>
<span style="font-size:10.0pt;color:#204A87">(9:03:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>MinGW performance issues & update <br>
<span style="font-size:10.0pt;color:#204A87">(9:03:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>ICU library size (<a href="https://bugreports.qt-project.org/browse/QTBUG-29828">https://bugreports.qt-project.org/browse/QTBUG-29828</a>)<br>
<span style="font-size:10.0pt;color:#204A87">(9:03:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Autotests on src packages (can those be removed)<br>
<span style="font-size:10.0pt;color:#204A87">(9:03:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Next meeting<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:04:08 AM) </span><b><span style="color:#AF7F00">tronical:
</span></b>akseli: pong<br>
<span style="font-size:10.0pt;color:#05353E">(9:04:17 AM) </span><span style="color:#05353E">thiago:
</span>ok<br>
<span style="font-size:10.0pt;color:#204A87">(9:04:18 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Any additional items for the agenda?<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:04:30 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: qt creator 2.7.0 for 5.0.2?<br>
<span style="font-size:10.0pt;color:#204A87">(9:04:51 AM) </span><b><span style="color:#204A87">akseli:
</span></b>kkoehne_home: good point, noted<br>
<span style="font-size:10.0pt;color:#7F2762">(9:05:17 AM) </span><span style="color:#7F2762">iieklund:
</span>ok, I'll start<br>
<span style="font-size:10.0pt;color:#7F2762">(9:05:34 AM) </span><span style="color:#7F2762">iieklund:
</span>installers are available in the same place as before<br>
<span style="font-size:10.0pt;color:#7F2762">(9:05:47 AM) </span><span style="color:#7F2762">iieklund:
</span>two new reference installers added<br>
<span style="font-size:10.0pt;color:#7F2762">(9:05:56 AM) </span><span style="color:#7F2762">iieklund:
</span>msvc2010 (32bit) opengl<br>
<span style="font-size:10.0pt;color:#7F2762">(9:06:07 AM) </span><span style="color:#7F2762">iieklund:
</span>and msvc2012 64bit / Win8<br>
<span style="font-size:10.0pt;color:#7F2762">(9:06:30 AM) </span><span style="color:#7F2762">iieklund:
</span>the content though is not up to date as things are blocked in ci<br>
<span style="font-size:10.0pt;color:#7F2762">(9:06:59 AM) </span><span style="color:#7F2762">iieklund:
</span>but feel free to test the installers, especially the new reference installers<br>
<span style="font-size:10.0pt;color:#062585">(9:07:23 AM) </span><b><span style="color:#062585">***thiago
</span></b>will try one of them if he has the time<br>
<span style="font-size:10.0pt;color:#7F2762">(9:07:35 AM) </span><span style="color:#7F2762">iieklund:
</span>and the installers will be uploaded to mirror brain in near future<br>
<span style="font-size:10.0pt;color:#4B7200">(9:07:37 AM) </span><span style="color:#4B7200">fkleint:
</span>OPenGL looks good, except that Creator was built against 5.0.1<br>
<span style="font-size:10.0pt;color:#062585">(9:07:41 AM) </span><b><span style="color:#062585">***ZapB
</span></b>will try the msvc2010 opengl one later today<br>
<span style="font-size:10.0pt;color:#4B7200">(9:07:42 AM) </span><span style="color:#4B7200">fkleint:
</span>thanks for that<br>
<span style="font-size:10.0pt;color:#7F2762">(9:07:48 AM) </span><span style="color:#7F2762">iieklund:
</span>fkleint: yes<br>
<span style="font-size:10.0pt;color:#7F2762">(9:08:00 AM) </span><span style="color:#7F2762">iieklund:
</span>kakoehne: did you change the qt version in confs already?<br>
<span style="font-size:10.0pt;color:#7F2762">(9:08:10 AM) </span><span style="color:#7F2762">iieklund:
</span>kkoehne_home: ^<br>
<span style="font-size:10.0pt;color:#711614">(9:08:13 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: Yes, next round should be build with 5.0.2<br>
<span style="font-size:10.0pt;color:#7F2762">(9:08:18 AM) </span><span style="color:#7F2762">iieklund:
</span>ok, thanks<br>
<span style="font-size:10.0pt;color:#7F2762">(9:08:59 AM) </span><span style="color:#7F2762">iieklund:
</span>that's the status briefly.....I will send email to lists when we start uploading packages to mirror brain<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:09:13 AM) </span><b><span style="color:#AF7F00">ramotyka:
</span></b>akseli: pong<br>
<span style="font-size:10.0pt;color:#711614">(9:09:19 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: Alright, so we distribute already candidate packages? Nice.<br>
<span style="font-size:10.0pt;color:#7F2762">(9:09:28 AM) </span><span style="color:#7F2762">iieklund:
</span>yes<br>
<span style="font-size:10.0pt;color:#711614">(9:09:44 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: But then we should really list the SHAs somewhere.<br>
<span style="font-size:10.0pt;color:#7F2762">(9:10:01 AM) </span><span style="color:#7F2762">iieklund:
</span>hmm, or I would say snapshots<br>
<span style="font-size:10.0pt;color:#7F2762">(9:10:07 AM) </span><span style="color:#7F2762">iieklund:
</span>maybe not release candidates<br>
<span style="font-size:10.0pt;color:#204A87">(9:10:17 AM) </span><b><span style="color:#204A87">akseli:
</span></b>not release candidates yet, snapshots<br>
<span style="font-size:10.0pt;color:#7F2762">(9:10:20 AM) </span><span style="color:#7F2762">iieklund:
</span><a href="http://origin.releases.qt-project.org/digia/5.0.2/">http://origin.releases.qt-project.org/digia/5.0.2/</a><br>
<span style="font-size:10.0pt;color:#05353E">(9:10:40 AM) </span><span style="color:#05353E">thiago:
</span>they are release candidates, but we don't tag them anymore<br>
<span style="font-size:10.0pt;color:#05353E">(9:10:45 AM) </span><span style="color:#05353E">thiago:
</span>people didn't like them last time around<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:11:30 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli, iieklund: Whatever you call em :) Still, how about having an md5sum.txt in
<a href="http://origin.releases.qt-project.org/digia/5.0.2/latest/">http://origin.releases.qt-project.org/digia/5.0.2/latest/</a> ?<br>
<span style="font-size:10.0pt;color:#7F2762">(9:11:59 AM) </span><span style="color:#7F2762">iieklund:
</span>kkoehne_home: good point, I'll check when I'll automate that<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:12:05 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli, iieklund: Just one command on the server: md5sum *>md5sum.txt<br>
<span style="font-size:10.0pt;color:#7F2762">(9:12:10 AM) </span><span style="color:#7F2762">iieklund:
</span>yep :)<br>
<span style="font-size:10.0pt;color:#7F2762">(9:12:47 AM) </span><span style="color:#7F2762">iieklund:
</span>next?<br>
<span style="font-size:10.0pt;color:#204A87">(9:12:57 AM) </span><b><span style="color:#204A87">akseli:
</span></b>how about opengl and webkit2? there was some discussion about those earlier... tronical^<br>
<span style="font-size:10.0pt;color:#4B7200">(9:13:13 AM) </span><span style="color:#4B7200">fkleint:
</span>Fixed already, I hope ;-)<br>
<span style="font-size:10.0pt;color:#711614">(9:13:33 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: So is there a webkit2 in the opengl packages now?<br>
<span style="font-size:10.0pt;color:#4B7200">(9:13:50 AM) </span><span style="color:#4B7200">fkleint:
</span>No, only kidding. but WebKit 1 examples work<br>
<span style="font-size:10.0pt;color:#4B7200">(9:14:05 AM) </span><span style="color:#4B7200">fkleint:
</span>Jocezlyn told me it is a bit involved, order of manweeks<br>
<span style="font-size:10.0pt;color:#711614">(9:14:42 AM) </span><span style="color:#711614">kkoehne_home:
</span>Okay, so something IMO for the known issues.<br>
<span style="font-size:10.0pt;color:#2D7647">(9:14:44 AM) </span><span style="color:#2D7647">tronical:
</span>agreed with Jocelyn :)<br>
<span style="font-size:10.0pt;color:#05353E">(9:15:12 AM) </span><span style="color:#05353E">thiago:
</span>so no webkit2 in the opengl package?<br>
<span style="font-size:10.0pt;color:#2D7647">(9:15:37 AM) </span><span style="color:#2D7647">tronical:
</span>note: it's not a very hard piece of work to do and it doesn't require webkit knowledge I think. so it could be done by anyone with a particular interest in this configuration ;-)<br>
<span style="font-size:10.0pt;color:#4B7200">(9:16:08 AM) </span><span style="color:#4B7200">fkleint:
</span>Urm, if you fix qwizard_win in return ...<br>
<span style="font-size:10.0pt;color:#2D7647">(9:16:18 AM) </span><span style="color:#2D7647">tronical:
</span>doesn't require windows knowledge? ;-)<br>
<span style="font-size:10.0pt;color:#2D7647">(9:16:45 AM) </span><span style="color:#2D7647">tronical:
</span>I guess I couldn't run away from that ;). anyway, just thought I'd point that out<br>
<span style="font-size:10.0pt;color:#4B7200">(9:16:54 AM) </span><span style="color:#4B7200">fkleint:
</span>but, it would be preferable if the WebkIt team did it, I guess<br>
<span style="font-size:10.0pt;color:#2D7647">(9:17:08 AM) </span><span style="color:#2D7647">tronical:
</span>naturally this is a question of priorities and it appears to be of higher priority by the desktop gl folks that for the webkit folks :)<br>
<span style="font-size:10.0pt;color:#2D7647">(9:17:18 AM) </span><span style="color:#2D7647">tronical:
</span>that=than<br>
<span style="font-size:10.0pt;color:#4B7200">(9:17:59 AM) </span><span style="color:#4B7200">fkleint:
</span>yep, could the WebKit folks please adjust the priorities accordingly?<br>
<span style="font-size:10.0pt;color:#2D7647">(9:18:27 AM) </span><span style="color:#2D7647">tronical:
</span>well, we argue that there are other things that are more important (that was exactly my point)<br>
<span style="font-size:10.0pt;color:#2D7647">(9:18:48 AM) </span><span style="color:#2D7647">tronical:
</span>(ok, I can't speak for the entire team, so the "we" is not a fair word to use)<br>
<span style="font-size:10.0pt;color:#4B7200">(9:20:35 AM) </span><span style="color:#4B7200">fkleint:
</span>ok, this would probably have to be discussed in another meeting, but for the ordinary WebKit users priorities would be 1) make OpnGL fly 2) reduce/scrap ICU dependency on Windows 3) reduce overall library size.<br>
<span style="font-size:10.0pt;color:#711614">(9:20:54 AM) </span><span style="color:#711614">kkoehne_home:
</span>Alright, given the schedule of 5.0.2 and the ETA 'of manweeks' it seems unrealistic for 5.0.2 anyway.<br>
<span style="font-size:10.0pt;color:#204A87">(9:21:02 AM) </span><b><span style="color:#204A87">akseli:
</span></b>in case opengl packages won't have webkit1 can we all live with that and release opengl package with Qt 5.0.2 release?<br>
<span style="font-size:10.0pt;color:#4B7200">(9:21:20 AM) </span><span style="color:#4B7200">fkleint:
</span>They have WebKit 1, but not WebKit 2<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:21:21 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: they have webkit1, just not webkit2<br>
<span style="font-size:10.0pt;color:#05353E">(9:21:34 AM) </span><span style="color:#05353E">thiago:
</span>what functionality gets suppressed with webkit2 being missing?<br>
<span style="font-size:10.0pt;color:#4B7200">(9:21:35 AM) </span><span style="color:#4B7200">fkleint:
</span>I think this is ok, known issue <br>
<span style="font-size:10.0pt;color:#204A87">(9:21:37 AM) </span><b><span style="color:#204A87">akseli:
</span></b>fklkeint: sorry, webkit2<br>
<span style="font-size:10.0pt;color:#2D7647">(9:21:39 AM) </span><span style="color:#2D7647">tronical:
</span>thiago: the qml2 integration<br>
<span style="font-size:10.0pt;color:#05353E">(9:22:06 AM) </span><span style="color:#05353E">thiago:
</span>so it means no webkit in qtquick2?<br>
<span style="font-size:10.0pt;color:#2D7647">(9:22:13 AM) </span><span style="color:#2D7647">tronical:
</span>yep<br>
<span style="font-size:10.0pt;color:#05353E">(9:22:28 AM) </span><span style="color:#05353E">thiago:
</span>that needs to be in the release notes<br>
<span style="font-size:10.0pt;color:#204A87">(9:24:12 AM) </span><b><span style="color:#204A87">akseli:
</span></b>sounds like a decision, opengl & webkit2 status needs to be made clear on release notes when time comes if not fixed.<br>
<span style="font-size:10.0pt;color:#AD7FA8">(9:24:20 AM) </span><span style="color:#AD7FA8">ZapB:
</span>+1<br>
<span style="font-size:10.0pt;color:#204A87">(9:24:42 AM) </span><b><span style="color:#204A87">akseli:
</span></b>next item: Qt Creator 2.7.0 for Qt 5.0.2<br>
<span style="font-size:10.0pt;color:#204A87">(9:25:55 AM) </span><b><span style="color:#204A87">akseli:
</span></b>both are aimed to be released quite closely .. I guess we should try to synch those releases somehow. any risks from that? kkoehne_home ^<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:26:26 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: Talked to eike. RIght now it seems 2.7.0 will be released indeed in two weeks.<br>
<span style="font-size:10.0pt;color:#4B7200">(9:26:44 AM) </span><span style="color:#4B7200">fkleint:
</span>Well, one should not delay the other I would say. I am not sure what the status of QBS support is<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:26:46 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: It has some improvements for qt 5.0, namely support for the Qt Quick2 Designer<br>
<span style="font-size:10.0pt;color:#4B7200">(9:26:58 AM) </span><span style="color:#4B7200">fkleint:
</span>andre is not here...<br>
<span style="font-size:10.0pt;color:#711614">(9:27:12 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: I talked to Eike and Andre, and they're fine with trying.<br>
<span style="font-size:10.0pt;color:#711614">(9:27:26 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: If we don't have an RC this Friday we may still revert the decision.<br>
<span style="font-size:10.0pt;color:#4B7200">(9:27:31 AM) </span><span style="color:#4B7200">fkleint:
</span>oki<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:28:08 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: So I propose switching to creator 2.7 branch, whith the option to revert if 2.7 RC doesn't make it this Friday.<br>
<span style="font-size:10.0pt;color:#7F2762">(9:28:19 AM) </span><span style="color:#7F2762">iieklund:
</span>kkoehne_home: is the qt / toolchain registration "api" the same in 2.7? No need to update qt/toolchain registration in installscripts?<br>
<span style="font-size:10.0pt;color:#711614">(9:28:27 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: No, that should be the same.<br>
<span style="font-size:10.0pt;color:#7F2762">(9:28:30 AM) </span><span style="color:#7F2762">iieklund:
</span>ok<br>
<span style="font-size:10.0pt;color:#4B7200">(9:28:39 AM) </span><span style="color:#4B7200">fkleint:
</span>[famous last words]<br>
<span style="font-size:10.0pt;color:#711614">(9:28:41 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: The only additional work is getting the qml2puppet packaged & installed<br>
<span style="font-size:10.0pt;color:#7F2762">(9:28:49 AM) </span><span style="color:#7F2762">iieklund:
</span>ah, that one<br>
<span style="font-size:10.0pt;color:#711614">(9:29:07 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: I'm looking into this.<br>
<span style="font-size:10.0pt;color:#7F2762">(9:29:11 AM) </span><span style="color:#7F2762">iieklund:
</span>ok, thanks<br>
<span style="font-size:10.0pt;color:#204A87">(9:29:38 AM) </span><b><span style="color:#204A87">akseli:
</span></b>sounds like a plan, let's try to have creator 2.7.0 & qt 5.0.2 synchronized and check status for that on e.g. next tuesday<br>
<span style="font-size:10.0pt;color:#204A87">(9:30:07 AM) </span><b><span style="color:#204A87">akseli:
</span></b>next item: MinGW performance issues & update for that?<br>
<span style="font-size:10.0pt;color:#204A87">(9:30:30 AM) </span><b><span style="color:#204A87">akseli:
</span></b>I think this have been discussed to be fixed on Qt 5.1.0 - am I right?
<br>
<span style="font-size:10.0pt;color:#4B7200">(9:30:35 AM) </span><span style="color:#4B7200">fkleint:
</span>What exactly are the issues?<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:30:40 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: That would be my proposal.<br>
<span style="font-size:10.0pt;color:#711614">(9:31:15 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: Turned out that the exception handling model of the current toolchain (SJLJ) has quite some performance impact.<br>
<span style="font-size:10.0pt;color:#711614">(9:31:27 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: E.g. creator startup times are about 20%-25% slower.<br>
<span style="font-size:10.0pt;color:#711614">(9:31:39 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: That's mostly due to QtCore being compiled with exceptions on.<br>
<span style="font-size:10.0pt;color:#711614">(9:31:54 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: ^^ Btw, what's the reason for that again?<br>
<span style="font-size:10.0pt;color:#4B7200">(9:32:14 AM) </span><span style="color:#4B7200">fkleint:
</span>Hm, first time I hear it<br>
<span style="font-size:10.0pt;color:#4B7200">(9:32:29 AM) </span><span style="color:#4B7200">fkleint:
</span>I think we have some try {} catch in destructors/event loops?<br>
<span style="font-size:10.0pt;color:#711614">(9:32:30 AM) </span><span style="color:#711614">kkoehne_home:
</span>fkleint: there's an alternative exception model (dw2), which has issues if you throw exceptions through stacks with e.g. Windows dlls (windows callbacks).
<br>
<span style="font-size:10.0pt;color:#05353E">(9:32:42 AM) </span><span style="color:#05353E">thiago:
</span>SJLJ requires a call to setjmp() in each exception-starting block<br>
<span style="font-size:10.0pt;color:#05353E">(9:32:47 AM) </span><span style="color:#05353E">thiago:
</span>it's active<br>
<span style="font-size:10.0pt;color:#05353E">(9:33:04 AM) </span><span style="color:#05353E">thiago:
</span>or was the question why QtCore has exceptions enabled?<br>
<span style="font-size:10.0pt;color:#05353E">(9:33:45 AM) </span><span style="color:#05353E">thiago:
</span>also, exceptions through windows code is not a problem<br>
<span style="font-size:10.0pt;color:#711614">(9:34:00 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Yes, why it's enabled. <br>
<span style="font-size:10.0pt;color:#05353E">(9:34:02 AM) </span><span style="color:#05353E">thiago:
</span>exceptions travelling through non-C++ code is unspecified behaviour. We've warned people about that.<br>
<span style="font-size:10.0pt;color:#05353E">(9:34:23 AM) </span><span style="color:#05353E">thiago:
</span>it's enabled in QtCore because some classes in it are supposed to be exception-safe<br>
<span style="font-size:10.0pt;color:#05353E">(9:34:27 AM) </span><span style="color:#05353E">thiago:
</span>especially the tool classes<br>
<span style="font-size:10.0pt;color:#711614">(9:35:00 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Okay.<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:35:55 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: So to summarize, I'd like to change the toolchain to a dw2 based one for 5.1. I personally think we can live with the current one for 5.0.2, unless someone feels strongly about it.<br>
<span style="font-size:10.0pt;color:#05353E">(9:36:26 AM) </span><span style="color:#05353E">thiago:
</span>keep the current one for now<br>
<span style="font-size:10.0pt;color:#05353E">(9:36:31 AM) </span><span style="color:#05353E">thiago:
</span>it's an ABI change, so better warn people<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:36:47 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: There's a slight chance that we can even use it also to update the gcc version (depending on when gcc 4.8 is out)<br>
<span style="font-size:10.0pt;color:#05353E">(9:37:28 AM) </span><span style="color:#05353E">thiago:
</span>gcc 4.8 will probably be out around May<br>
<span style="font-size:10.0pt;color:#05353E">(9:37:35 AM) </span><span style="color:#05353E">thiago:
</span>too late for 5.1 probably<br>
<span style="font-size:10.0pt;color:#204A87">(9:38:01 AM) </span><b><span style="color:#204A87">akseli:
</span></b>so decision is that mingw toolchain change will be handled on 5.1 and not changed for 5.0.2?<br>
<span style="font-size:10.0pt;color:#2D7647">(9:38:06 AM) </span><span style="color:#2D7647">tronical:
</span>thiago: isn't it even worse, that setjmp is called for each function that may require any cleanup (i.e. has objects on the stack and then calls other functions)?<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:38:14 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: I think so.<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:38:15 AM) </span><b><span style="color:#AF7F00">ZapB:
</span></b>akseli: sounds sensible<br>
<span style="font-size:10.0pt;color:#05353E">(9:38:34 AM) </span><span style="color:#05353E">thiago:
</span>tronical: yes, any exception block. Not just try {} catch {}.<br>
<span style="font-size:10.0pt;color:#2D7647">(9:38:50 AM) </span><span style="color:#2D7647">tronical:
</span>ah, that's what you mean with exception block. right :)<br>
<span style="font-size:10.0pt;color:#05353E">(9:38:50 AM) </span><span style="color:#05353E">thiago:
</span>any object with a destructor calling a function that may throw requires a call to setjmp.<br>
<span style="font-size:10.0pt;color:#05353E">(9:38:56 AM) </span><span style="color:#05353E">thiago:
</span>it's horrible.<br>
<span style="font-size:10.0pt;color:#2D7647">(9:39:00 AM) </span><span style="color:#2D7647">tronical:
</span>agreed!<br>
<span style="font-size:10.0pt;color:#2D7647">(9:39:05 AM) </span><span style="color:#2D7647">tronical:
</span>(iOS is using it, btw - on arm :)<br>
<span style="font-size:10.0pt;color:#05353E">(9:39:11 AM) </span><span style="color:#05353E">thiago:
</span>ugh!<br>
<span style="font-size:10.0pt;color:#05353E">(9:39:14 AM) </span><span style="color:#05353E">thiago:
</span>stupid<br>
<span style="font-size:10.0pt;color:#2D7647">(9:39:27 AM) </span><span style="color:#2D7647">tronical:
</span>mostly stupid for C++, great for objective C :)<br>
<span style="font-size:10.0pt;color:#05353E">(9:39:41 AM) </span><span style="color:#05353E">thiago:
</span>anyway<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:39:50 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: Next point? :)<br>
<span style="font-size:10.0pt;color:#204A87">(9:39:53 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Next item: ICU library size (e.g. <a href="https://bugreports.qt-project.org/browse/QTBUG-29828">
https://bugreports.qt-project.org/browse/QTBUG-29828</a>) ^^ <br>
<span style="font-size:10.0pt;color:#7F2762">(9:40:09 AM) </span><span style="color:#7F2762">iieklund:
</span>yes<br>
<span style="font-size:10.0pt;color:#7F2762">(9:40:27 AM) </span><span style="color:#7F2762">iieklund:
</span>the icudt49 is about 18mb<br>
<span style="font-size:10.0pt;color:#7F2762">(9:40:39 AM) </span><span style="color:#7F2762">iieklund:
</span>it should be possible to reduce the size of that<br>
<span style="font-size:10.0pt;color:#AD7FA8">(9:40:41 AM) </span><span style="color:#AD7FA8">ZapB:
</span>ouch<br>
<span style="font-size:10.0pt;color:#05353E">(9:40:57 AM) </span><span style="color:#05353E">thiago:
</span>has anyone measured?<br>
<span style="font-size:10.0pt;color:#711614">(9:41:06 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Measured what?<br>
<span style="font-size:10.0pt;color:#7F2762">(9:41:11 AM) </span><span style="color:#7F2762">iieklund:
</span>kai have you looked into ICU Data customizer<br>
<span style="font-size:10.0pt;color:#7F2762">(9:41:12 AM) </span><span style="color:#7F2762">iieklund:
</span>?<br>
<span style="font-size:10.0pt;color:#711614">(9:41:33 AM) </span><span style="color:#711614">kkoehne_home:
</span>well, there's <a href="http://apps.icu-project.org/datacustom/">http://apps.icu-project.org/datacustom/</a> , where you can just deselect stuff :)<br>
<span style="font-size:10.0pt;color:#7F2762">(9:41:56 AM) </span><span style="color:#7F2762">iieklund:
</span>yes, but what we can deselect :) ?<br>
<span style="font-size:10.0pt;color:#711614">(9:41:57 AM) </span><span style="color:#711614">kkoehne_home:
</span>The hard question is what is actually used by Qt at all, and which one might be used, but is not important.<br>
<span style="font-size:10.0pt;color:#05353E">(9:42:15 AM) </span><span style="color:#05353E">thiago:
</span>measured if it can be made smaller<br>
<span style="font-size:10.0pt;color:#05353E">(9:42:25 AM) </span><span style="color:#05353E">thiago:
</span>that's the question: what can we de-select?<br>
<span style="font-size:10.0pt;color:#711614">(9:42:30 AM) </span><span style="color:#711614">kkoehne_home:
</span>My approach would be to try to come up with a profile that matches our Qt 4.x features.<br>
<span style="font-size:10.0pt;color:#05353E">(9:42:35 AM) </span><span style="color:#05353E">thiago:
</span>timezone data, for example<br>
<span style="font-size:10.0pt;color:#711614">(9:42:56 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Well, there's this 5.1 patch that will make use of some of it?<br>
<span style="font-size:10.0pt;color:#05353E">(9:43:17 AM) </span><span style="color:#05353E">thiago:
</span>QtCore uses it only for codecs and and collation<br>
<span style="font-size:10.0pt;color:#711614">(9:43:28 AM) </span><span style="color:#711614">kkoehne_home:
</span>I can come up with a proposal based on best measure. But I doubt that we have extensive coverage in autotests.<br>
<span style="font-size:10.0pt;color:#05353E">(9:43:29 AM) </span><span style="color:#05353E">thiago:
</span>5.1 will use the timezone data, if john finishes his work<br>
<span style="font-size:10.0pt;color:#05353E">(9:43:40 AM) </span><span style="color:#05353E">thiago:
</span>the question is: what does webkit need it for?<br>
<span style="font-size:10.0pt;color:#711614">(9:43:53 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: ^^ :)<br>
<span style="font-size:10.0pt;color:#2D7647">(9:44:19 AM) </span><span style="color:#2D7647">tronical:
</span>thiago: line breaking for example<br>
<span style="font-size:10.0pt;color:#2D7647">(9:44:25 AM) </span><span style="color:#2D7647">tronical:
</span>thiago: not calendaring, etc.<br>
<span style="font-size:10.0pt;color:#2D7647">(9:44:34 AM) </span><span style="color:#2D7647">tronical:
</span>thiago: generally speaking unicode properties of characters<br>
<span style="font-size:10.0pt;color:#711614">(9:44:46 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: So if you go to <a href="http://apps.icu-project.org/datacustom/">
http://apps.icu-project.org/datacustom/</a> , which of the top sections do we need at all?<br>
<span style="font-size:10.0pt;color:#2D7647">(9:44:47 AM) </span><span style="color:#2D7647">tronical:
</span>collaction, too, I think<br>
<span style="font-size:10.0pt;color:#2D7647">(9:45:28 AM) </span><span style="color:#2D7647">tronical:
</span>kkoehne_home: can't say 100%, but I think break iterator, collators and maybe charset mapping tables<br>
<span style="font-size:10.0pt;color:#062585">(9:46:10 AM) </span><b><span style="color:#062585">***tronical
</span></b>quickly double checks collation. but I'm sure about break iterator and charset mapping (codecs)<br>
<span style="font-size:10.0pt;color:#2D7647">(9:46:20 AM) </span><span style="color:#2D7647">tronical:
</span>ACK, collaction is also used by webkit<br>
<span style="font-size:10.0pt;color:#2D7647">(9:46:52 AM) </span><span style="color:#2D7647">tronical:
</span>what's in misc? :)<br>
<span style="font-size:10.0pt;color:#711614">(9:47:35 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: e.g. timezone data, it seems<br>
<span style="font-size:10.0pt;color:#05353E">(9:47:41 AM) </span><span style="color:#05353E">thiago:
</span>btw, I don't know where u_strToCase is in<br>
<span style="font-size:10.0pt;color:#05353E">(9:47:48 AM) </span><span style="color:#05353E">thiago:
</span>I assumed it was in collator. You need to verify.<br>
<span style="font-size:10.0pt;color:#711614">(9:48:06 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Okay, will do.<br>
<span style="font-size:10.0pt;color:#711614">(9:48:18 AM) </span><span style="color:#711614">kkoehne_home:
</span>is it safe to assume that we only need the official supported languages?<br>
<span style="font-size:10.0pt;color:#05353E">(9:48:31 AM) </span><span style="color:#05353E">thiago:
</span>it seems to come from uloc.h<br>
<span style="font-size:10.0pt;color:#711614">(9:48:34 AM) </span><span style="color:#711614">kkoehne_home:
</span>e.g. that we can drop zone/km.res (Kmehr)<br>
<span style="font-size:10.0pt;color:#05353E">(9:48:35 AM) </span><span style="color:#05353E">thiago:
</span>no<br>
<span style="font-size:10.0pt;color:#05353E">(9:48:38 AM) </span><span style="color:#05353E">thiago:
</span>we need all languages<br>
<span style="font-size:10.0pt;color:#05353E">(9:49:12 AM) </span><span style="color:#05353E">thiago:
</span>but we can trim the codec list to the same as the built-in codecs<br>
<span style="font-size:10.0pt;color:#711614">(9:49:53 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: well, the currency, language, timezone information in misc is already 6,6MB<br>
<span style="font-size:10.0pt;color:#711614">(9:50:04 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: We somehow managed with less in Qt 4 times :)<br>
<span style="font-size:10.0pt;color:#05353E">(9:50:28 AM) </span><span style="color:#05353E">thiago:
</span>because we used whateve came with the OS<br>
<span style="font-size:10.0pt;color:#711614">(9:50:59 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: So we don't have this fallback any more, at all?<br>
<span style="font-size:10.0pt;color:#05353E">(9:51:05 AM) </span><span style="color:#05353E">thiago:
</span>if webkit didn't need it, I'd suggest turning off the codecs<br>
<span style="font-size:10.0pt;color:#05353E">(9:51:16 AM) </span><span style="color:#05353E">thiago:
</span>and turn off qicucodec<br>
<span style="font-size:10.0pt;color:#05353E">(9:52:08 AM) </span><span style="color:#05353E">thiago:
</span>QLocale::to{Upper,Lower} has no fallback: we need the localisation tables<br>
<span style="font-size:10.0pt;color:#05353E">(9:52:13 AM) </span><span style="color:#05353E">thiago:
</span>QCollator requires the collation tables<br>
<span style="font-size:10.0pt;color:#711614">(9:52:23 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: We should clarify with Lars. I thought his intend was to rather get rid of the internal QtCore ones. But I might be wrong.<br>
<span style="font-size:10.0pt;color:#05353E">(9:52:34 AM) </span><span style="color:#05353E">thiago:
</span>yes, we need to get rid of the internal QtCore wes<br>
<span style="font-size:10.0pt;color:#05353E">(9:52:36 AM) </span><span style="color:#05353E">thiago:
</span>ones<br>
<span style="font-size:10.0pt;color:#05353E">(9:52:42 AM) </span><span style="color:#05353E">thiago:
</span>we haven't done that yet, though<br>
<span style="font-size:10.0pt;color:#711614">(9:53:01 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Anyway, it feels stupid to ship the whole world for a small helloworld. Maybe we can come up with two profiles, and let the user decide when he packages his app.<br>
<span style="font-size:10.0pt;color:#05353E">(9:53:02 AM) </span><span style="color:#05353E">thiago:
</span>the point is that we now have functionality that requires ICU. New functionality that wasn't there before.<br>
<span style="font-size:10.0pt;color:#711614">(9:53:22 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Functionality that a lot of users don't care about, and shouldn't pay for.<br>
<span style="font-size:10.0pt;color:#05353E">(9:53:29 AM) </span><span style="color:#05353E">thiago:
</span>we could ship a small, stub library too that supports English and basic codecs<br>
<span style="font-size:10.0pt;color:#05353E">(9:53:35 AM) </span><span style="color:#05353E">thiago:
</span>no other locales, no other codecs<br>
<span style="font-size:10.0pt;color:#05353E">(9:53:54 AM) </span><span style="color:#05353E">thiago:
</span>make it REALLY basic so no one gets ideas about shipping it in any context where internationalisation is required<br>
<span style="font-size:10.0pt;color:#711614">(9:54:04 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Okay, that sounds actually good.<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:54:20 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: I'll actually try it out, and send a proposal to the mailing list.<br>
<span style="font-size:10.0pt;color:#062585">(9:54:22 AM) </span><b><span style="color:#062585">***tronical
</span></b>thought it was always a strength of Qt that i18n worked out of the box<br>
<span style="font-size:10.0pt;color:#05353E">(9:54:32 AM) </span><span style="color:#05353E">thiago:
</span>note this will affect webkit too: it might not be able to decode webpages in certain codecs<br>
<span style="font-size:10.0pt;color:#204A87">(9:54:34 AM) </span><b><span style="color:#204A87">akseli:
</span></b>kkoehne_home: ok, thank you<br>
<span style="font-size:10.0pt;color:#204A87">(9:54:55 AM) </span><b><span style="color:#204A87">akseli:
</span></b>then next item: Autotests on src packages (can those be removed)<br>
<span style="font-size:10.0pt;color:#204A87">(9:55:04 AM) </span><b><span style="color:#204A87">akseli:
</span></b>Autotests in src packages (can those be removed): we are currently shipping src packages with autotests. is there any reason why those couldn't be removed from src packages?<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:55:04 AM) </span><b><span style="color:#AF7F00">thiago:
</span></b>akseli: keep them there<br>
<span style="font-size:10.0pt;color:#711614">(9:55:12 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Right. But would you go to Qt 5 if you don't have immediate benefits, but additional dependencies of about 15 MB , for your small app?<br>
<span style="font-size:10.0pt;color:#204A87">(9:55:12 AM) </span><b><span style="color:#204A87">akseli:
</span></b>ok, why?<br>
<span style="font-size:10.0pt;color:#AD7FA8">(9:55:22 AM) </span><span style="color:#AD7FA8">ZapB:
</span>can we make this icu customisation tool part of the deployment/internationalisation somehow? i.e. allow people to build their own versin for their needs<br>
<span style="font-size:10.0pt;color:#711614">(9:55:48 AM) </span><span style="color:#711614">kkoehne_home:
</span>ZapB: It's here: <a href="http://apps.icu-project.org/datacustom/">http://apps.icu-project.org/datacustom/</a><br>
<span style="font-size:10.0pt;color:#711614">(9:56:06 AM) </span><span style="color:#711614">kkoehne_home:
</span>ZapB: NOt sure whether there's any benefit of having it in a separate domain, too.<br>
<span style="font-size:10.0pt;color:#2D7647">(9:56:18 AM) </span><span style="color:#2D7647">tronical:
</span>kkoehne_home: that's the same argument as to why we decided to go unicode all over the place in Qt and let QFont not have a charset: most developers don't understand the complexity behind supporting more than just the western world. and they shouldn't.
 it's a strenght of Qt that they don't have to worry about that stuff at all but can cater to users on the entire planet.<br>
<span style="font-size:10.0pt;color:#AD7FA8">(9:56:28 AM) </span><span style="color:#AD7FA8">ZapB:
</span>kkoehne_home: sure but I mean to be run automagically somehow<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:57:11 AM) </span><b><span style="color:#AF7F00">thiago:
</span></b>akseli: people run tests<br>
<span style="font-size:10.0pt;color:#AF7F00">(9:57:15 AM) </span><b><span style="color:#AF7F00">thiago:
</span></b>akseli: therefore, keep them in the source<br>
<span style="font-size:10.0pt;color:#711614">(9:57:35 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Sure. But again, some developers don't want to support more than just the western world, or even their own company PC's :)<br>
<span style="font-size:10.0pt;color:#711614">(9:57:42 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Let's give them the choice.<br>
<span style="font-size:10.0pt;color:#05353E">(9:57:55 AM) </span><span style="color:#05353E">thiago:
</span>kkoehne_home: I'm not talking about "Western World"<br>
<span style="font-size:10.0pt;color:#2D7647">(9:57:58 AM) </span><span style="color:#2D7647">tronical:
</span>kkoehne_home: I think that's a very limited viewpoint of our customers<br>
<span style="font-size:10.0pt;color:#05353E">(9:58:02 AM) </span><span style="color:#05353E">thiago:
</span>kkoehne_home: I'm being serious: make it work for *English*<br>
<span style="font-size:10.0pt;color:#05353E">(9:58:12 AM) </span><span style="color:#05353E">thiago:
</span>kkoehne_home: let it fail for German too. Then people will not get ideas.<br>
<span style="font-size:10.0pt;color:#711614">(9:58:21 AM) </span><span style="color:#711614">kkoehne_home:
</span>thiago: Okay.<br>
<span style="font-size:10.0pt;color:#05353E">(9:58:32 AM) </span><span style="color:#05353E">thiago:
</span>kkoehne_home: for example, failing to uppercase "ö" to "Ö"<br>
<span style="font-size:10.0pt;color:#2D7647">(9:58:36 AM) </span><span style="color:#2D7647">tronical:
</span>It's Qt's job to make life easier for developers, not to make them have to learn about codecs and complexities of languages<br>
<span style="font-size:10.0pt;color:#711614">(9:58:50 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Maybe, but there's the fact that people complain. A lot. <br>
<span style="font-size:10.0pt;color:#05353E">(9:59:07 AM) </span><span style="color:#05353E">thiago:
</span>kkoehne_home: QString("köhne").toUpper() == "KöHNE"<br>
<span style="font-size:10.0pt;color:#2D7647">(9:59:18 AM) </span><span style="color:#2D7647">tronical:
</span>kkoehne_home: that doesn't make them representative for the entire user base of Qt. what about all the users in say asia that are happy that this works out of the box and are therefore not complaining?<br>
<span style="font-size:10.0pt;color:#711614">(9:59:24 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Fine with me. You might have noticed that I write myself with oe for these reasons :)<br>
<span style="font-size:10.0pt;color:#711614">(9:59:53 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Alright. I'm even fine with using the fully icu by default. let's just ship a stripped down version as a drop-in replacement, too.<br>
<span style="font-size:10.0pt;color:#711614">(10:00:23 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical, thiago: Let's move this to the mailing list. <br>
<span style="font-size:10.0pt;color:#2D7647">(10:00:33 AM) </span><span style="color:#2D7647">tronical:
</span>kkoehne_home: right, opt-in for those who make a conscious _choice_ about limiting themselves to less functionality is good IMHO. making that opt-in easy that is<br>
<span style="font-size:10.0pt;color:#711614">(10:01:12 AM) </span><span style="color:#711614">kkoehne_home:
</span>ZapB: Maging that magically: The real issue isn't the selection website, but compiling your own ICU afterwards.<br>
<span style="font-size:10.0pt;color:#2D7647">(10:01:17 AM) </span><span style="color:#2D7647">tronical:
</span>kkoehne_home: so the developer who wants to write that little app can easily switch to a smaller "package" after he noticed that it's too big for his taste :)<br>
<span style="font-size:10.0pt;color:#711614">(10:01:34 AM) </span><span style="color:#711614">kkoehne_home:
</span>tronical: Yes :)<br>
<span style="font-size:10.0pt;color:#204A87">(10:01:53 AM) </span><b><span style="color:#204A87">akseli:
</span></b>ICU topic continues on mailing list then.. lets check status of that on next meeting<br>
<span style="font-size:10.0pt;color:#05353E">(10:02:34 AM) </span><span style="color:#05353E">thiago:
</span>when do you propose?<br>
<span style="font-size:10.0pt;color:#204A87">(10:02:51 AM) </span><b><span style="color:#204A87">akseli:
</span></b>about autotests in src packages: does all agree that those are needed in src packages and should stay there?
<br>
<span style="font-size:10.0pt;color:#7F2762">(10:03:12 AM) </span><span style="color:#7F2762">iieklund:
</span>autotests in src packages, was it decided to keep them?<br>
<span style="font-size:10.0pt;color:#AF7F00">(10:03:14 AM) </span><b><span style="color:#AF7F00">kkoehne_home:
</span></b>akseli: This is 5.1 material anyway, give me some time :)<br>
<span style="font-size:10.0pt">(10:03:50 AM) </span><b>hanne [<i>~linaae@84.49.38.202</i>] entered the room.</b><br>
<span style="font-size:10.0pt;color:#711614">(10:04:22 AM) </span><span style="color:#711614">kkoehne_home:
</span>iieklund: I think we always had them. + I guess maybe the .pro files would need adoption if they woulnd't be there.<br>
<span style="font-size:10.0pt;color:#7F2762">(10:04:49 AM) </span><span style="color:#7F2762">iieklund:
</span>hmm yes I remember there was some dependency to autotests?<br>
<span style="font-size:10.0pt;color:#7F2762">(10:05:06 AM) </span><span style="color:#7F2762">iieklund:
</span>ok, se we keep them then<br>
<span style="font-size:10.0pt;color:#204A87">(10:05:56 AM) </span><b><span style="color:#204A87">akseli:
</span></b>alright, next meeting: proposing to have on next Tuesday 08:00 CET. We should then have installers with content up to date, results from those and also Creator 2.7 RC where to base decisions<br>
<span style="font-size:10.0pt;color:#05353E">(10:06:06 AM) </span><span style="color:#05353E">thiago:
</span>I cannot join any time next week<br>
<span style="font-size:10.0pt;color:#05353E">(10:06:14 AM) </span><span style="color:#05353E">thiago:
</span>so feel free to choose an European-friendly time<br>
<span style="font-size:10.0pt;color:#AD7FA8">(10:06:49 AM) </span><span style="color:#AD7FA8">ZapB:
</span>an hour later would be good for me :)<br>
<span style="font-size:10.0pt;color:#711614">(10:07:10 AM) </span><span style="color:#711614">kkoehne_home:
</span>Both 8:00 and 9:00 CET is fine with me.<br>
<span style="font-size:10.0pt;color:#7F2762">(10:07:12 AM) </span><span style="color:#7F2762">iieklund:
</span>09:00 CET is fine for me<br>
<span style="font-size:10.0pt;color:#204A87">(10:08:17 AM) </span><b><span style="color:#204A87">akseli:
</span></b>09:00 CET sounds like a plan, i will send invitations later today<br>
<span style="font-size:10.0pt;color:#AF7F00">(10:08:41 AM) </span><b><span style="color:#AF7F00">ZapB:
</span></b>akseli: thanks<br>
<span style="font-size:10.0pt;color:#204A87">(10:08:41 AM) </span><b><span style="color:#204A87">akseli:
</span></b>i guess that was all, thank you all for the meeting:)<o:p></o:p></p>
</div>
</body>
</html>