Re: [MeeGo-dev] [meego-releases] New Bugzilla product MeeGo Distribution Packages has been created.
ext Zhao, Fan fan.z...@intel.com writes: The purpose of the MeeGo Distribution Packages product is to provide an option for people to report/triage bugs to packages, and it's setup for 1.3 bug reporting at this moment. Creating a new product is nice, but it is different from moving existing bugs into it en masse. This mass moving was not announced, as far as I can see. It is impolite to massively move bugs around without cooperating with the 'owners' of those bugs. Or maybe I misunderstand. In any case, the direction is right, so maybe we can live with some bumps on the way. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product MeeGo Distribution Packages has been created.
Wednesday, June 29, 2011 3:13 PM Marius Vollmer wrote: ext Zhao, Fan fan.z...@intel.com writes: The purpose of the MeeGo Distribution Packages product is to provide an option for people to report/triage bugs to packages, and it's setup for 1.3 bug reporting at this moment. Creating a new product is nice, but it is different from moving existing bugs into it en masse. This mass moving was not announced, as far as I can see. It is impolite to massively move bugs around without cooperating with the 'owners' of those bugs. Or maybe I misunderstand. In any case, the direction is right, so maybe we can live with some bumps on the way. Mass movement of bugs is not expected at this moment. Maybe 1.2.1 release is a good timing to do that. Currently, let's start from reporting/triaging new 1.3 bugs to that product when we have the needs. Thanks, Fan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product MeeGo Distribution Packages has been created.
ext Zhao, Fan fan.z...@intel.com writes: Wednesday, June 29, 2011 3:13 PM Marius Vollmer wrote: ext Zhao, Fan fan.z...@intel.com writes: The purpose of the MeeGo Distribution Packages product is to provide an option for people to report/triage bugs to packages, and it's setup for 1.3 bug reporting at this moment. Creating a new product is nice, but it is different from moving existing bugs into it en masse. This mass moving was not announced, as far as I can see. It is impolite to massively move bugs around without cooperating with the 'owners' of those bugs. Or maybe I misunderstand. In any case, the direction is right, so maybe we can live with some bumps on the way. Mass movement of bugs is not expected at this moment. So why is Michael saying the following then: I wondered why bugs for our component, the virtual keyboard, were moved to newly created components without prior announcement, nor explanations. Here is an example of a bug that was moved without a comment: https://bugs.meego.com/show_activity.cgi?id=15554 Anyway, none of my business, so I shut up. :) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product MeeGo Distribution Packages has been created.
Hi, On 6/29/11 11:33 AM, ext Zhao, Fan fan.z...@intel.com wrote: Wednesday, June 29, 2011 4:15 PM Marius Vollmer wrote: ext Zhao, Fan fan.z...@intel.com writes: Wednesday, June 29, 2011 3:13 PM Marius Vollmer wrote: ext Zhao, Fan fan.z...@intel.com writes: The purpose of the MeeGo Distribution Packages product is to provide an option for people to report/triage bugs to packages, and it's setup for 1.3 bug reporting at this moment. Creating a new product is nice, but it is different from moving existing bugs into it en masse. This mass moving was not announced, as far as I can see. It is impolite to massively move bugs around without cooperating with the 'owners' of those bugs. Or maybe I misunderstand. In any case, the direction is right, so maybe we can live with some bumps on the way. Mass movement of bugs is not expected at this moment. So why is Michael saying the following then: I wondered why bugs for our component, the virtual keyboard, were moved to newly created components without prior announcement, nor explanations. Here is an example of a bug that was moved without a comment: https://bugs.meego.com/show_activity.cgi?id=15554 Anyway, none of my business, so I shut up. :) I just did a search, around 15 VKB bugs were moved to the new product, so I don't think it's mass movement. If there are problems for that component, let's solve the specific problem, but let's not overshade the general direction. The point here isn't about the administrative task of moving bugs with the change several bugs at once bugzilla feature but making sure that an appropriate comment is attached to the bugs. So I guess you could remind anyone on your side involved into moving the bugs that it's mandatory to at least put a comment with the reasoning behind the action. In this case, yanshuang.zh...@intel.com needs to be reminded. Doing so will generate an email notification to anyone having incentive on the bug. Of course, announcements on the ML are good but as we all know, it's simply not enough as Michael and Marius point out... Thanks for bringing it up anyway. Another point is that one could actually challenge why some bugs were moved there if the purpose is to monitor 1.3 release. IMHO anything done already doesn't need to move, does it? Just verified and closed is largely enough. Thanks, Fan Cheers, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to get display resolution using Qt or QtMobility
Em Wednesday, 29 de June de 2011, às 10:37:56, Stylianou, Costas escreveu: Hi, What's the recommended way to get the width and height of your device's screen in MeeGo? QDesktopWidget::screenGeometry http://doc.qt.nokia.com/latest/qdesktopwidget.html#screenGeometry -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product MeeGo Distribution Packages has been created.
On 6/29/2011 2:05 AM, eric.le-r...@nokia.com wrote: So I guess you could remind anyone on your side involved into moving the bugs that it's mandatory to at least put a comment with the reasoning behind the action. so as a user of bugzilla I strongly disagree with your statement. I use the filter bug mail feature so that I only get bugmail on important events (real new information added, not just noisy bookkeeping things) that feature gets completely and utterly destroyed if the QA person, in addition to the actual change, also puts in I changed this as comment. (and that comment adds absolutely zero value) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [meego-releases] New Bugzilla product MeeGo Distribution Packages has been created.
On Wed, 2011-06-29 at 06:41 -0700, Arjan van de Ven wrote: On 6/29/2011 2:05 AM, eric.le-r...@nokia.com wrote: So I guess you could remind anyone on your side involved into moving the bugs that it's mandatory to at least put a comment with the reasoning behind the action. so as a user of bugzilla I strongly disagree with your statement. I use the filter bug mail feature so that I only get bugmail on important events (real new information added, not just noisy bookkeeping things) that feature gets completely and utterly destroyed if the QA person, in addition to the actual change, also puts in I changed this as comment. (and that comment adds absolutely zero value) True for trivial stuff like CC or Assignee changes (plus that's configurable in personal bugmail settings). Wrong for on-trivial stuff like this case (moving a larger bunch of reports to a completely different product and not finding bug reports anymore by querying for only the previous product). Adding a moving to product $blah as announced in $mailing-list-post-url; filter for this comment isn't hard, and filtering your bugmail for it isn't either, right? andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] GLES v1/v2 -- compliance
For the purposes of compliance is only GLESv2 required, or is v1 also required? If the latter, we have an issue to figure out in that there seems to be some variance in library names (the Mesa version is /usr/lib/libGLESv1_CM.so.1 and the EMGD version is /usr/lib/libGLES_CM.so.1) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Touch events
Hi: I am trying to find out how to receive touch events. There are QGestureEvent and also QEvent::TouchBegin, QEvent::TouchEnd. I am not able to get those going. It seems that mouse event has no issues, but not touch. Is there another way Qt interacts with touch screen? thanks Mark ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Meego-qa] Poor decision making in MeeGo, again ...
On Wed, 2011-06-29 at 11:08 +0800, Fu, Elva wrote: I remembered Wanshuang announced the change previously. Here is the link http://lists.meego.com/pipermail/meego-qa/2011-June/001958.html Seems like you missed a part of Michael's initial email so I'll quote that part again: Discussing this issue on the relevant mailing list (Read: Where the developers are. Hint: It's not the QA ML) would have been the minimum requirement. And once a decision is made, you also need to publicly announce it. No you cannot expect me (or anyone else who is *not* in your QA team) to read your miles-long thread on your QA ML (http://www.mail-archive.com/meego-qa@lists.meego.com/msg01561.html). You're welcome. ;-) andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Detailed comparison results for Maemo 5 Fremantle and MeeGo 1.2 Harmattan
Hi, oh, wow, no libsdl anymore. So the list of apps not portable to MeeGo includes all gtk apps, all hildon apps, all non-qml qt apps and now all sdl apps. I still hope that some of these will return in form of community ports. Till Am Mittwoch 29 Juni 2011 schrieb Andrey Ponomarenko: Hi, This message is intended for those who are interested in porting applications from Maemo 5.0 Fremantle to MeeGo 1.2 Harmattan. The Maemo release team has already published the differences between the corresponding versions of SDK [1]. I would like to extend them by our comparison results from the binary-compatibility point of view [2-3] performed by the abi-compliance-checker tool. Hope this will be helpful for someone. Thanks. [1] Differences between Fremantle Update7 and Harmattan Beta SDK releases http://harmattan-dev.nokia.com/unstable/beta/Fremantle_Update7_vs_Harmattan_Beta_content_comparison.html [2] Binary compatibility between Maemo 5.0 and MeeGo 1.2 Harmattan on ARM http://linuxtesting.org/compatibility/Maemo_5.0_to_MeeGo_1.2_Harmattan/arm/abi_compat_report.html [3] Compatibility testing for embedded operating systems/Maemo http://linuxtesting.org/compatibility/ ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] 1.3 MeeGo release schedule posted
Hey all, Just fyi, the 1.3 release schedule is posted up on the wiki: http://wiki.meego.com/Release_Engineering/Plans/1.3 Main dates are: MM2: Jul 26 - Intrusive (high risk and priority) changes phase complete MM3: Aug 23 - Feature development phase complete MM4: Oct 04 - Branch 1.3 - Stabilization phase complete MM5: Oct 27 - 1.3 Release Thanks, Release Engineering ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] FW: Bug triage process updated
FYI. Don't be surprised that the bugs are reported or triaged to the package product, and you don't need to scared because the old triaged bugs won't be moved at this moment. We will just focus on 1.3 new bugs to see if the package product would help developers to get bugs more effectively. Thanks, Fan -Original Message- From: Zhao, Fan Sent: Thursday, June 30, 2011 11:52 AM To: meego...@lists.meego.com; Collaboration list for Release Engineering and QA teams (moderated discussion list) Subject: Bug triage process updated I just updated bug triage process a little bit to reflect how bug triage teams are going to triage bugs when the new MeeGo Distribution Packages product is added. Basically the scope is expanded a little bit that bug triage team will try to assign bug to packages listed in MeeGo Distribution Packages product whenever possible (apply for new incoming 1.3 bugs only at this moment). Details available @ http://wiki.meego.com/Quality/Bugtriage. Thanks, Fan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
