From frederik.gladhorn at theqtcompany.com Mon Apr 11 16:50:18 2016 From: frederik.gladhorn at theqtcompany.com (Frederik Gladhorn) Date: Mon, 11 Apr 2016 16:50:18 +0200 Subject: [Releasing] [Development] Qt 5.7.0 beta snapshot available - gtk 3 and packaging on RHEL 6 In-Reply-To: References: Message-ID: <2184572.tYyMDLlE42@frederik-thinkcentre-m93p> Hello all, for Linux packaging we currently use a Red Hat 6 which seemed like a good compromise at the time. I have been pondering https://bugreports.qt.io/browse/QTBUG-52259 for a while and don't seem to reach a conclusion. We had a contribution porting our gtk 2 theme to gtk 3 (thanks Dmitry!). The question is how to proceed, from what I can tell, it's not trivial to get gtk3 built on rhel6. For Linux distributions this is of course not a problem, but the Qt installer is currently built without any gtk plugin compiled. In the future (Qt 5.8), I'd like to switch to rhel 7 as packaging platform, so this problem should go away. For Qt 5.7, the options seem to be: 1.) ignore the problem and ship Qt packages in the installer without gtk theme 2.) revert the patch to have the gtk2 theme for one release longer and only have gtk3 with Qt 5.8 3.) package on rhel 7, but I'm told, we're already too late in the cycle Any ideas appreciated. In general I have a hard time seeing how to cleanly create packages on Linux, unless we basically ship an entire distro (similar to Chrome and others)... I'd love to learn about good approaches, since packaging on something "old enough to run everywhere" and "new enough to allow all dependencies to be built" seems hard to achieve. Sadly we don't have the resources to create native packages for each and every distro (we want to allow our users to use Qt on older releases of their favorite distro) and I'm not sure if packagers would be willing to help us get into a situation where it's easy to create packages for all relevant distributions, installing into custom prefixes and having a mix of versions. So for the time being I have been convinced that creating the installers is valuable for many people on Linux, but I wonder if there's a way we can do better. Cheers, Frederik PS: there are some more issues with old distros and packaging... gstreamer 0.10 comes to mind, next to bluez dependencies. On Monday, April 11, 2016 12:47:03 PM Heikkinen Jani wrote: > Hi all, > > > We have new Qt 5.7.0 beta snapshot available > > > Windows: http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/407/ > > Linux: http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/389/ > > Src:http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/latest_src/ (Under > mirroring) > > > Mac packages are still missing, retry is ongoing. Please test the packages & > report your findings in Jira. We need good testing coverage now to see how > close the beta we are. We are trying to get beta out as soon as possible > and so on we need to know all beta blockers at the moment. So please make > sure all beta beta blockers have '5.7.0 beta' in Fix Version(s) -field & so > on visible in beta blocker list > (https://bugreports.qt.io/issues/?filter=17576) > > > Windows and Linux packages are RTA smoke tested & seems to be pretty much > OK. > > > Known issues from the packages:https://bugreports.qt.io/issues/?filter=17601 > > > br, > > Jani From perezmeyer at gmail.com Mon Apr 11 18:37:03 2016 From: perezmeyer at gmail.com (Lisandro =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer) Date: Mon, 11 Apr 2016 13:37:03 -0300 Subject: [Releasing] [Development] Qt 5.7.0 beta snapshot available - gtk 3 and packaging on RHEL 6 In-Reply-To: <2184572.tYyMDLlE42@frederik-thinkcentre-m93p> References: <2184572.tYyMDLlE42@frederik-thinkcentre-m93p> Message-ID: <4210863.E4Rg9Zd13E@luna> On Monday 11 April 2016 16:50:18 Frederik Gladhorn wrote: > Hello all, [snip] > For Qt 5.7, the options seem to be: > 1.) ignore the problem and ship Qt packages in the installer without gtk > theme 2.) revert the patch to have the gtk2 theme for one release longer > and only have gtk3 with Qt 5.8 > 3.) package on rhel 7, but I'm told, we're already too late in the cycle > > Any ideas appreciated. I'll leave the above unanswered because I think I'm not the right one for that question. > In general I have a hard time seeing how to cleanly > create packages on Linux, unless we basically ship an entire distro (similar > to Chrome and others)... I'd love to learn about good approaches, since > packaging on something "old enough to run everywhere" and "new enough to > allow all dependencies to be built" seems hard to achieve. I guess here that you are talking about "cleanness" with respect to dependencies. We distro maintainers normally know that this is not easily solvable except bundling half of them, which is in turn ugly. It basically boils down to "one size does not fits all". > Sadly we don't have the resources to create native packages for each and > every distro (we want to allow our users to use Qt on older releases of > their favorite distro) and I'm not sure if packagers would be willing to > help us get into a situation where it's easy to create packages for all > relevant distributions, installing into custom prefixes and having a mix of > versions. With my Debian maintainer hat on the most complicated thing would be to avoid conflicting with existing distro installations. qtchooser can help here tough. One thing to have in mind: if a user gets qt by using the online installer/whatever method coming from you directly and sets it as default Qt installation it will have problems with distro apps that uses Qt's private headers. > So for the time being I have been convinced that creating the installers is > valuable for many people on Linux, but I wonder if there's a way we can do > better. I would really be interested here to have actual numbers. We in Debian can provide backports if the situation merits it. So far I only see one or two people asking us for Qt backports in a year. But maybe that doesn't reflects the real necessity for it. Yes, I understand that here I'm proposing having distro-provided packages instead of getting the installations from you directly, but I think that's our job if there is really people interested in them out there. It might be interesting to say that most of the request of having up-to-date Qt in stable (or old stable) Debian releases comes from people working at/for companies and not from other developers. I'm of course possibly biased in my answers so *please* do not hesitate in asking/proposing other things, I might be missing the elephant in the room. If there is anything we can do to improve the situation for our users in a win-win way then we need to consider it. -- "So long, and thanks for all the fish!" The Hitchhickers guide to the Galaxy Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part. URL: From jani.heikkinen at theqtcompany.com Tue Apr 12 12:48:33 2016 From: jani.heikkinen at theqtcompany.com (Heikkinen Jani) Date: Tue, 12 Apr 2016 10:48:33 +0000 Subject: [Releasing] [Development] Qt 5.7.0 beta snapshot available - gtk 3 and packaging on RHEL 6 In-Reply-To: <4210863.E4Rg9Zd13E@luna> References: <2184572.tYyMDLlE42@frederik-thinkcentre-m93p>, <4210863.E4Rg9Zd13E@luna> Message-ID: On Monday 11 April 2016 16:50:18 Frederik Gladhorn wrote: > Hello all, [snip] > For Qt 5.7, the options seem to be: > 1.) ignore the problem and ship Qt packages in the installer without gtk > theme 2.) revert the patch to have the gtk2 theme for one release longer > and only have gtk3 with Qt 5.8 > 3.) package on rhel 7, but I'm told, we're already too late in the cycle > > Any ideas appreciated. 1 or 2, As Frederik wrote it is too late for 3). I propose we just ship beta with 1) and if there isnt big complains use that option with 5.7. And if there is then just revert the patch between beta and RC br, Jani ________________________________________ Lähettäjä: Development käyttäjän puolestaLisandro Damián Nicanor Pérez Meyer Lähetetty: 11. huhtikuuta 2016 19:37 Vastaanottaja: development at qt-project.org; releasing Aihe: Re: [Development] Qt 5.7.0 beta snapshot available - gtk 3 and packaging on RHEL 6 On Monday 11 April 2016 16:50:18 Frederik Gladhorn wrote: > Hello all, [snip] > For Qt 5.7, the options seem to be: > 1.) ignore the problem and ship Qt packages in the installer without gtk > theme 2.) revert the patch to have the gtk2 theme for one release longer > and only have gtk3 with Qt 5.8 > 3.) package on rhel 7, but I'm told, we're already too late in the cycle > > Any ideas appreciated. I'll leave the above unanswered because I think I'm not the right one for that question. > In general I have a hard time seeing how to cleanly > create packages on Linux, unless we basically ship an entire distro (similar > to Chrome and others)... I'd love to learn about good approaches, since > packaging on something "old enough to run everywhere" and "new enough to > allow all dependencies to be built" seems hard to achieve. I guess here that you are talking about "cleanness" with respect to dependencies. We distro maintainers normally know that this is not easily solvable except bundling half of them, which is in turn ugly. It basically boils down to "one size does not fits all". > Sadly we don't have the resources to create native packages for each and > every distro (we want to allow our users to use Qt on older releases of > their favorite distro) and I'm not sure if packagers would be willing to > help us get into a situation where it's easy to create packages for all > relevant distributions, installing into custom prefixes and having a mix of > versions. With my Debian maintainer hat on the most complicated thing would be to avoid conflicting with existing distro installations. qtchooser can help here tough. One thing to have in mind: if a user gets qt by using the online installer/whatever method coming from you directly and sets it as default Qt installation it will have problems with distro apps that uses Qt's private headers. > So for the time being I have been convinced that creating the installers is > valuable for many people on Linux, but I wonder if there's a way we can do > better. I would really be interested here to have actual numbers. We in Debian can provide backports if the situation merits it. So far I only see one or two people asking us for Qt backports in a year. But maybe that doesn't reflects the real necessity for it. Yes, I understand that here I'm proposing having distro-provided packages instead of getting the installations from you directly, but I think that's our job if there is really people interested in them out there. It might be interesting to say that most of the request of having up-to-date Qt in stable (or old stable) Debian releases comes from people working at/for companies and not from other developers. I'm of course possibly biased in my answers so *please* do not hesitate in asking/proposing other things, I might be missing the elephant in the room. If there is anything we can do to improve the situation for our users in a win-win way then we need to consider it. -- "So long, and thanks for all the fish!" The Hitchhickers guide to the Galaxy Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ From jani.heikkinen at theqtcompany.com Wed Apr 13 07:41:24 2016 From: jani.heikkinen at theqtcompany.com (Heikkinen Jani) Date: Wed, 13 Apr 2016 05:41:24 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 12.4.2016 Message-ID: Meeting minutes from Qt Release Team meeting 12th April 2016 Qt 5.7.0 Beta status: - New snapshot under testing, nothing really serious reported so far * Mostly packaging issues found, should be fixed in next snapshot. QTBUG-52517 is the hardest one & most probably will be as known issue in beta (affects only in 32bit windows packages, 64 bit ones are OK) - Target is to get new snapshot for testing during this week & release it as Qt 5.7.0 Beta if nothing really serious found during testing * Beta target beginning of next week Qt 5.6.1 status: - First snapshot under RTA testing, seems to be pretty OK - Target to produce new snapshot quite soon * Plan to start manual testing when Qt 5.7.0 beta is out - Target to get Qt 5.6.1 out at the beginning of May * To be able to do this we need to start soft branching Mon 18th April & finalize it after a week (as usual) Next meeting Tue 26th April 16:00 CET br, Jani irc log below: [17:00:24] akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche: ping [17:00:30] jaheikki3: pong [17:00:46] jaheikki3: pong [17:01:03] poing [17:02:18] Time to start qt release team meeting [17:02:23] on agenda today: [17:02:27] aheikki3L: pong [17:02:29] - Qt 5.7 beta status [17:02:47] - Qt 5.6.1 status [17:02:57] Any additional item to the agenda? [17:04:40] ok, lets start from Qt 5.7 beta status [17:05:11] - Beta snapshot packages under testing, nothing really critical reported so far [17:05:29] mostly packaging issues which should be fixed in next snapshot [17:05:49] Open beta blockers in https://bugreports.qt.io/issues/?filter=17576 [17:07:01] Biggest issue there is QTBUG-52517 Qt5.7 offline: WebEngine and WebView libraries missing from vs2013 & vs2015 #406 installers. this might be hard to be fixed soon [17:08:03] It is because we are still buiding 32 bit binaries in 32 bit windows & webengine needs 64 bit machine even for 32 bit build [17:08:28] So most probably we need to live with that issue in beta & fix it for RC [17:08:46] jaheikki3: This is 32bit packages only? [17:09:04] fkleint: Yes, 64 bit packages are ok [17:09:10] Ah,right [17:09:18] since I saw nanobrowser.. [17:10:45] We are targeting to get new snapshot later this week and if nothing really serious found during testing I propose to release those as 5.7 beta at the beginning of next week [17:11:34] sounds good to me [17:11:37] Any comments or questions? [17:13:54] Ok, that was all about 5.7 beta at the moment [17:14:09] Then Qt 5.6.1 status: [17:14:48] - First snapshot created last week & under RTA testing [17:15:28] from 5.6 branch as is? [17:15:30] - RTA smoke tests done, seems to be pretty much OK. Full RTA set ongoing [17:15:37] fkleint: Yes [17:15:40] oki [17:16:08] when is it targeted to and will new snapshots be taken? [17:16:27] We aren't planning to organize official manual testing round for 5.6.1 packages yet to get all effort for 5.7 beta first [17:17:16] carewolf: I would say 5.6.1 out somewhere beginning of May [17:17:56] and we are trying to produce new snapshot quite soon. First manual test round targeted after 5.7 beta release [17:18:13] thanks [17:18:31] and if someone wants to take a tour packages are found from http://download.qt.io/snapshots/qt/5.6/5.6.1/ [17:19:51] If we are trying to release 5.6.1 at the beginning of may we should start branching from 5.6 to 5.6.1 quite soon. I propose to start soft branching at the beginning of next week & finalize it after a week (as usual), ok? [17:20:16] +1 [17:20:20] +1 [17:21:30] Ok, that is the plan then [17:23:00] That was all at this time so let's end this meeting now. If we managed to get beta out at the beginning of next week I think we can skip the next weeks meeting & have new one 26th April, OK? [17:23:25] sounds good [17:23:31] yes [17:23:50] Great. Thanks for your participation. Bye! [17:24:07] bye [17:24:59] bye -------------- next part -------------- An HTML attachment was scrubbed... URL: From releasing at qt-project.org Mon Apr 18 23:45:22 2016 From: releasing at qt-project.org (rrir) Date: Tue, 19 Apr 2016 05:45:22 +0800 Subject: [Releasing] releasing:h7mmy Message-ID: <20160419054534482425@jpeswwr.com> 项目管理实战操作 时·间·地·点： 2016年4月26-27日 上海 参·加·对·象： 项目总监、部门经理、高级项目经理、项目团队成员等，特别适合正在从事项目管理的人员 授·课·方·式： 讲师讲授 + 视频演绎 + 案例研讨 +角色扮演 + 讲师点评 学·习·费·用： 5200元/两天（含两天中餐、指定教材、茶点） 垂·询·热·线：021-31006787 18917870808 联·系·邮·箱：jsqyxuxin at vip.163.com QQ/微信:320588808 课程背景： 随着市场竞争的日益加剧，企业只靠维持现状的执行系统越来越不能满足不断变化的市场需求，因而项目管理也越来越受到企业的重视。本课程通过讲师讲解、案例分析、小组讨论、学员练习等授课方式，给你带来全新的思维视角，让深陷项目困扰的你蓦然回首、茅塞顿开。整个课程远离理论上的说教，而是强调如何把项目管理的工具和技巧应用到实际的项目中去，去解决项目管理过程中经常出现的范围不清、质量缺陷、进度拖期等具体问题。 课程收益： 对企业而言，我们确保学员在培训完成后，大家能用同一种理念，同一种方法，同一种图解，同一种表格来完成项目。 1、参训的每一位学员培训后都将培养成具有以下,项目经理必备的,三种能力： A、确定范围 B、在范围内完成任务的可置信度 C、分析趋势的能力 课程大纲: 第一天 一、项目及项目管理 什么叫项目 项目的特点 什么叫管理 什么叫项目管理 课堂练习 回答参加者问题 学员练习： 做练习题 讨论 学员提问 二、项目及其所处的环境分析 项目中投资人与项目经理的关系 项目经理的职责 项目中利害关系人分析 项目早期估算的一般工具 项目阶段图和资源图的制作方法 讨论 提问 三、项目沟通管理 项目的横向沟通 项目中跨部门协调的问题解决方法 项目的归属和项目目标SMART分析方法 项目管理的发展历史 项目工作陈述表的制作方法 提问 做跨部门协调表格练习 课堂作业： 完成项目启动阶段的“二图一表” 完成案例中的“阶段图”、“资源图”和“工作陈述表” 第二天： 四、项目范围管理（WBS 和RAM 的制作方法和规定） 项目的工作分解结构（WBS） WBS的评估方法 WBS中的注意事项 一个完整的WBS系统应该达到什么目的 项目的责任矩阵表(RAM) 布置课堂作业（学员案例中的WBS和RAM ） 提问 交流 每人做案例模拟的开头3个模块 课堂作业： 完成项目范围阶段的“一图一表” 课堂完成案例中的WBS和RAM 五、项目时间管理（网络图的基本制作方法） 制作任务与任务之间的逻辑网络图（PDM，ADM，GERT，Network Board）的四种方法 讨论所做的案例 发表对项目时间管理的看法 根据项目时间管理的规定，各自发表个人的意见 六、项目时间管理（带有CPM网络图的制作方法） 课堂练习： 初级网络图制作 高级网络图内容及制作方法 小组练习 课堂练习---初级网络图制作 小组练习---以小组形式完成高级网络图等练习 七、项目时间管理（9大工具及CPM网络图的10大用途） 带有CPM的网络图的特点及十大功能 甘特图的作用 做阿尔法案例 总结项目时间管理的九大工具 解答学员问题 做阿尔法案例练习 学员提问 掌握项目经理必备的4个工具（WBS，RAM，CPM图，甘特图） 课程结束总结： 学员问题与答疑 项目“五图二表”的总结 布置课后作业 学员积极提问 收集完成回家作业的基本方法 讲师介绍：[刘毛华] 背景介绍： * 新活力企业管理顾问有限公司 高级讲师 * 上海交通大学液压传动工程学士， * 芬兰赫尔新基大学商学院硕士 * 剑桥大学国际培训师资质证书 * 曾担任普洛菲尔帕丝金属首席代表克空压机有限公司副总经理 * 匹克电子（上海）有限公司副总经理、怡和机器执行总经理 * 上海世博会事务协调局项目进度控制特邀专家 * 劳力士（中国）有限公司整体装修项目特邀项目总监 授课风格： 授课采用互动性双向交流方式，案例讨论、角色扮演、管理评估等皆能切合主题，以实例个案为骨干，辅以深厚学术理论基础；在教会学员如何正确使用管理工具的同时，注重传授给学员如何创建一种全新理念的管理平台，使其能够在这个平台上自由发挥和创新。 服务过的客户： 万科、世茂、BASF染料、普莱克斯气体、梅兰日兰电器有限公司、西门子开关、天津汉高洗洁剂、江南造船厂、西门子通讯、上海、医疗机械（中国）公司、菲利浦电子、伊莱克斯（长沙）公司、菲利浦半导体（广东）、卡特比勒起重机、上海万科地产、广达电脑、上海贝尔阿尔卡特、许继电器（国内上市公司）、上海电气集团公司、上海国药集团、3 M (中国)、上海通用照明、德尔福汽车电气（白城）、英国BP石油、上汽MBA研修班、大庆油田 （中，英文）、广州舒适刀片 、复星实业有限公司、爱默生电气（中国）有限公司、广东北电通讯（英文授课）、松下万宝（广州）有限公司、上海柴油机股份有限公司、通用医疗机械（北京）有限公司、北京百奥药业、广州白云化工、德尔福汽车电气（广州）、艾力（广州）包装系统有限公司、大众汽车变速器（上海）有限公司、飞利浦照明电子（上海）有限公司、上海汽车工业销售总公司、爱默生过程处理（中国）有限公司、上海氯碱股份有限公司、广东丽珠医药集团有限公司、湖北移动通信公司、招商银行(上海)、广东美的日用电器、威图电子机械（上海）有限公司、东莞科泰电子有限公司、美华认证（中国）有限公司、广州本田汽车有限公司等 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Thu Apr 21 12:06:08 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Thu, 21 Apr 2016 10:06:08 +0000 Subject: [Releasing] Qt 5.7.0 Beta released Message-ID: Hi all, Qt 5.7.0 Beta is released today, see http://blog.qt.io/blog/2016/04/21/qt-5-7-beta-released/ Big thanks for everyone involved! br, Jani Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Tue Apr 26 16:23:48 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 26 Apr 2016 14:23:48 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 Message-ID: Meeting minutes from Qt Release Team meeting 26th April 2016 Qt 5.7.0 status: - Beta released last Thursday - Schedule updated in https://wiki.qt.io/Qt-5.7-release * API Review May 2016 * String freeze 7th May 2016 * Branch 5.7.0 from 5.7 19th May 2016 * Release Candidate 1st June 2016 * Final Release 15th June 2016 - To be able to keep the schedule we need to make sure * All Qt 5.7.0 blockers are visible in https://bugreports.qt.io/issues/?filter=17619 (= Fix Version(s) contains 5.7.0 RC ) * All blockers are fixed as soon as possible. Please prioritise bugs in https://bugreports.qt.io/issues/?filter=17619 * Header diff is started during this week. Actions for that is already ongoing by Eddy, Fredrik (&Frederik) * Change files are done early enough. Maintainers, please create first versions now & update those later when needed! * Packages are tested properly when testing request comes. This is really essential: We need to find the blockers as early as possible! * We will fix all known issues before RC. * All fixes are in latest Mon 23rd May (to have enough time for getting qt5.git integrated,packages created & tested properly before RC) - First snapshot created after the beta. No manual test request coming at this time but can be found from http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/ Qt 5.6.1 status: - branching not started yet because of bugs in init-repository scripts. Fixes are integrating & branching will be start immediately when changes are in - New snapshot will be created when current qt5.git integration succeed. Target during this week - target to get 5.6.1 out as soon as possible but most probably it will be somewhere mid May * Blocker list for Qt 5.6.1: https://bugreports.qt.io/issues/?filter=17596. Some issue still open, hoping we could get those closed as soon as possible Next meeting Tue 10th May 16:00 CET irc log below: [17:01:03] akseli: iieklund: thiago: fkleint: ZapB: tronical: vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl: ablasche: ping [17:02:39] Time to start qt release team meeting [17:02:47] On agenda today: [17:02:53] Qt 5.7.0 status [17:02:59] Qt 5.6.1 status [17:03:11] Something else to the agenda? [17:03:19] jaheikki3: pong [17:04:11] agenda seems great, please continue [17:04:19] pong [17:04:33] Lets start from 5.7.0 status: [17:05:11] Beta released & schedule updated based on beta release date, see https://wiki.qt.io/Qt-5.7-release [17:05:53] * API Review May 2016 [17:05:53] * String freeze 7th May 2016 [17:05:53] * Branch 5.7.0 from 5.7 19th May 2016 [17:05:53] * Release Candidate 1st June 2016 [17:05:53] * Final Release 15th June 2016 [17:06:56] And to be able to keep this schedule we need to make sure: [17:07:42] *All Qt 5.7.0 blockers are visible in https://bugreports.qt.io/issues/?filter=17619 (= Fix Version(s) contains 5.7.0 RC ) [17:07:42] * All blockers are fixed as soon as possible. Please prioritise bugs in https://bugreports.qt.io/issues/?filter=17619 [17:07:42] * Header diff is started during this week. Actions for that is already ongoing by Eddy, Fredrik (&Frederik) [17:07:42] * Change files are done early enough. Maintainers, please create first versions now & update those later when needed! [17:07:42] * Packages are tested properly when testing request comes. This is really essential: We need to find the blockers as early as possible! [17:07:42] * We will fix all known issues before RC.* All fixes are in latest Mon 23rd May (to have enough time for getting qt5.git integrated,packages created & tested properly before RC) [17:08:58] And first snapshot already created after the beta. No manual test request coming at this time but can be found from http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/ [17:09:05] Any comments or questions? [17:11:11] Ok, that's all about 5.7 at this time [17:11:17] Then Qt 5.6.1 status: [17:11:40] branching from '5.6' to '5.6.1' not started yet because of bugs in init-repository scripts. Fixes are integrating & branching will be start immediately when changes are in [17:12:01] New snapshot will be created when current qt5.git integration succeed. Target during this week [17:12:33] target to get 5.6.1 out as soon as possible but most probably it will be somewhere mid May [17:12:53] Blocker list for Qt 5.6.1: https://bugreports.qt.io/issues/?filter=17596. Some issue still open, hoping we could get those closed as soon as possible [17:13:11] Any comments or questions? [17:15:34] Ok, it was pretty quiet at this time ;) [17:16:22] I think we can skip next week's meeting & have new one after two weeks [17:16:31] +1 [17:16:38] Then we should be pretty close to 5.6.1 [17:16:52] Great! Let's end this meeting now , bye! [17:17:06] bye [17:17:06] thanks Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io +358 50 4873735 http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhihn at gmx.com Tue Apr 26 16:52:43 2016 From: jhihn at gmx.com (Jason H) Date: Tue, 26 Apr 2016 16:52:43 +0200 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 In-Reply-To: References: Message-ID:   > Blocker list for Qt 5.6.1: https://bugreports.qt.io/issues/?filter=17596. Some issue still open, hoping we could get those closed as soon as possible How do we get issues posted to the blocker list? I am a commercial customer waiting on several issues. For 5.6 series: VERY IMPORTANT TO US: https://bugreports.qt.io/browse/QTBUG-49760 https://bugreports.qt.io/browse/QTBUG-51911 https://bugreports.qt.io/browse/QTBUG-51335 IMPORTANT: https://bugreports.qt.io/browse/QTBUG-52217 https://bugreports.qt.io/browse/QTBUG-47934 For 5.7 series: https://bugreports.qt.io/browse/QTBUG-51133 https://bugreports.qt.io/browse/QTBUG-52013 From jani.heikkinen at qt.io Wed Apr 27 06:55:14 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 27 Apr 2016 04:55:14 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 In-Reply-To: References: , Message-ID: Hi! Thanks for your feedback about the issues & importance of those from your point of view. I checked those issues and I have to say any of those won't block the Qt 5.6.1 release, sorry! All of those are p2 or even p3 issues and none of those aren't regression from Qt 5.6.0 release. Blockers are bad regressions, really bad usability issues etc and any of issue below cannot but in that category. But of course it would be good to get these fixed already in Qt 5.6.1. Those for 5.7 series: Those aren't bugs at all but new features and so on those should be implemented earliest in '5.8'. Feature Freeze for Qt 5.7.0 has been in effect quite long time already. Proposing issues in the release blocker list can be done by setting the release in the Fix Version(s) -field of the bug. So adding '5.6.1' as Fix Version(s) raises an issue as a blocker (proposal) for Qt 5.6.1 release. br, Jani ________________________________________ From: Jason H Sent: Tuesday, April 26, 2016 5:52 PM To: Jani Heikkinen Cc: releasing at qt-project.org Subject: Re: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 > Blocker list for Qt 5.6.1: https://bugreports.qt.io/issues/?filter=17596. Some issue still open, hoping we could get those closed as soon as possible How do we get issues posted to the blocker list? I am a commercial customer waiting on several issues. For 5.6 series: VERY IMPORTANT TO US: https://bugreports.qt.io/browse/QTBUG-49760 https://bugreports.qt.io/browse/QTBUG-51911 https://bugreports.qt.io/browse/QTBUG-51335 IMPORTANT: https://bugreports.qt.io/browse/QTBUG-52217 https://bugreports.qt.io/browse/QTBUG-47934 For 5.7 series: https://bugreports.qt.io/browse/QTBUG-51133 https://bugreports.qt.io/browse/QTBUG-52013 From jani.heikkinen at qt.io Wed Apr 27 08:52:56 2016 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 27 Apr 2016 06:52:56 +0000 Subject: [Releasing] Heads up - 5.7 soft string freeze Message-ID: Hi all, Qt 5.7 beta is out & work towards final release continues. One step on the way is String Freeze which is planned to happen 7th May 2016, see https://wiki.qt.io/Qt-5.7-release. So it is time to start keeping the translatable strings as it is and fix remaining important issues. Br, Jani Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikkinen at qt.io +358 50 4873735 http://qt.io [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhihn at gmx.com Wed Apr 27 15:58:18 2016 From: jhihn at gmx.com (Jason H) Date: Wed, 27 Apr 2016 15:58:18 +0200 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 In-Reply-To: References: , , Message-ID: Thanks Jani. I tried do to that, but I don't think the option was available to me? Would there be a difference between my open source and commercial support accounts? The airplane mode *IS* a regression AFAICT, from 5.5. Our QA efforts are hampered every day because we cannot test losing all connectivity and regaining it, without first exiting the app! There *seems* to be a fix available just recently? (We have long-running transfers, and 99% of the problems with our product are with connectivity) That particular bug is a big one for us. The rest I listed for 5.6 are just embarrassing, but do not affect functionality or quality. But they do prevent us from having a A+ app. > Sent: Wednesday, April 27, 2016 at 12:55 AM > From: "Jani Heikkinen" > To: "Jason H" > Cc: "releasing at qt-project.org" > Subject: Re: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 > > Hi! > > Thanks for your feedback about the issues & importance of those from your point of view. I checked those issues and I have to say any of those won't block the Qt 5.6.1 release, sorry! All of those are p2 or even p3 issues and none of those aren't regression from Qt 5.6.0 release. Blockers are bad regressions, really bad usability issues etc and any of issue below cannot but in that category. But of course it would be good to get these fixed already in Qt 5.6.1. > > Those for 5.7 series: Those aren't bugs at all but new features and so on those should be implemented earliest in '5.8'. Feature Freeze for Qt 5.7.0 has been in effect quite long time already. > > Proposing issues in the release blocker list can be done by setting the release in the Fix Version(s) -field of the bug. So adding '5.6.1' as Fix Version(s) raises an issue as a blocker (proposal) for Qt 5.6.1 release. > > br, > Jani > ________________________________________ > From: Jason H > Sent: Tuesday, April 26, 2016 5:52 PM > To: Jani Heikkinen > Cc: releasing at qt-project.org > Subject: Re: [Releasing] Meeting minutes from Qt Release Team meeting 26.4.2016 > > > Blocker list for Qt 5.6.1: https://bugreports.qt.io/issues/?filter=17596. Some issue still open, hoping we could get those closed as soon as possible > > How do we get issues posted to the blocker list? I am a commercial customer waiting on several issues. > > For 5.6 series: > VERY IMPORTANT TO US: > https://bugreports.qt.io/browse/QTBUG-49760 > https://bugreports.qt.io/browse/QTBUG-51911 > https://bugreports.qt.io/browse/QTBUG-51335 > > IMPORTANT: > https://bugreports.qt.io/browse/QTBUG-52217 > https://bugreports.qt.io/browse/QTBUG-47934 > > For 5.7 series: > https://bugreports.qt.io/browse/QTBUG-51133 > https://bugreports.qt.io/browse/QTBUG-52013 >