Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

Hi Joel, Thanks for the clearance. So, we can keep 1.2 to track 1.2.1 and need to add new release 1.2.0 for tracking 1.2.0 updates? Waiting until Monday to do the changes, so people can add their comments if needed. Lähettäjä: ext Clark, Joel [joel.cl...@

Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

But given the 1.2 branching naming conventions discussed by Rolla, it's not a 1.2 update, it's a 1.2.0 update. In fact if you look at the release naming for the May 19 release it was a 1.2.0 release. The 1.2 branch is under CCB for core stuff but continues with lots of changes for devices UX stu

Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

Hi Fan, It's true that 1.2.1 isn't released, but testing for it has already started. How we can track is the bug in the 1.2 update or in the 1.2.1 if there isn't any sign for that? Tracking that by the image names is too hard. Btw, I just read mailing conversation you and Daniel had in the rele

Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

> Sent: Friday, June 10, 2011 1:27 PM > ext-iekku.huttu...@nokia.com wrote: > > Hi Daniel, > > Sorry, I got a bit confused. Should we instead keep 1.2 to track it's update > blockers and just add 1.2.1 to track that and later it's updates? Would be the > most simple solution and wouldn't need tha

Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

Hi, iekku I think there are 2 ways to track 1.2.0/1.2.1 bugs: 1) Add 1.2.0 to track 1.2.0 update bugs, and keep 1.2 to track 1.2.1 bug. Before 1.2.1 is released, we can suppose current 1.2 branch is 1.2 trunk branch. After 1.2.1 is released, if we will continue to have 1.2.2 or later re

Re: [Meego-qa] [meego-releases] [update] 1.2 Release plan (1.2.0, 1.2.1)

Hi Daniel, > Friday, June 10, 2011 1:01 PM > Tao, Daniel wrote: > > Dear All > > In order to align with the new 1.2 release plan, I would like propose to add a > new value "1.2.0" in "MeeGo Release" field to track 1.2.0 update bugs. So in > "MeeGo Release" field, "1.2.0" will mean this bug is fo

Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

Hi Daniel, Sorry, I got a bit confused. Should we instead keep 1.2 to track it's update blockers and just add 1.2.1 to track that and later it's updates? Would be the most simple solution and wouldn't need that much changes in Bugzilla's current structure. Br, Iekku ___

Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release

Hi, iekku Thanks for your quick response. I agreed with you. For 1.2.1 release, we can add 1.2.0 to identify 1.2 update, and keep 1.2 to identify 1.2.1. After 1.2.1 is released, we can separate 1.2.1 as 1.2.1 update. Daniel From: meego-qa-boun...@lists.meego.com [mailto:meego-qa-boun...@lists

[Meego-qa] Filing bugs for MeeGo 1.2.1 release

Hi, For my understanding MeeGo 1.2.1 isn't straight update for 1.2, so I was wondering if it need's own release to the Bugzilla. I have already received questions from QA people what release they should mark when filing a new bug report. If we agree about the 1.2.1 as a new release in Bugzilla,

Re: [Meego-qa] [meego-releases] [update] 1.2 Release plan (1.2.0, 1.2.1)

Dear All In order to align with the new 1.2 release plan, I would like propose to add a new value "1.2.0" in "MeeGo Release" field to track 1.2.0 update bugs. So in "MeeGo Release" field, "1.2.0" will mean this bug is for 1.2.0 update and "1.2" means this bug is for 1.2 trunk/1.2.1. In this c

[Meego-qa] Test type change and impact on MCTS

Hi, I found new test type has been changed. So it seems to be time that MCTS also need to change to fix bug 17877. But I still have one issue: Some test suites are heavily dependent on testlink to export tests.xml. But currently testlink does not support new test type (bug 17768). Directly change

[Meego-qa] test set and impact on MCTS

Hi I found there is defintion for test set, there is a term "set" in test-definition, but I understand that it refers to http://wiki.meego.com/Quality/TestSetGuideline When I try release new mcts, I saw an new mwts package that are platform dependent, please see bug 18414 I hoped to be unique .xm

Re: [Meego-qa] BoF MeeGo Bugzilla Structure Enhancement Prototype in SF conference - Meeting minutes

> Wednesday, June 08, 2011 3:17 PM > eric.le-r...@nokia.com wrote > Hi Fan, > > On 6/7/11 5:00 PM, "ext Zhao, Fan" wrote: > > >Hi Eric, > > > >> Friday, June 03, 2011 6:22 PM > >> eric.le-r...@nokia.com wrote: > >> > >> Hi Fan, > >> > >> > >> On 6/1/11 5:23 PM, "ext Zhao, Fan" wrote: > >> > >>

Re: [Meego-qa] Follow-up of bugs on test type fix in testlink and mcts

On Thu, 2011-06-09 at 11:57 +0800, Zheng, Jeff wrote: > So these bugs are for mcts in meego 1.3, is it correct? > > Meego 1.2 has already released with old test type. > > Bests > Jeff > > > -Original Message- > > From: meego-qa-boun...@lists.meego.com > > [mailto:meego-qa-boun...@lists.m

Re: [Meego-qa] How to apply log-in account for http://qa-reports.meego.com/? Thanks

> Thursday, June 09, 2011 5:29 PM > Jarno Keskikangas wrote: > > Hi all, > > In order to get an account to QA Reports, please open a ticket as described in > the documentation: > http://wiki.meego.com/Quality/QA-tools/QAReports > > The registration up url should be kept confidential as all the s

Re: [Meego-qa] Default assignee "need-tri...@meego.com"

Hi Shuang, On Thu, 2011-06-09 at 20:09 +0800, Wan, Shuang wrote: > Hello Andre, > > > -Original Message- > > From: Andre Klapper [mailto:aklap...@openismus.com] > > Sent: Thursday, June 09, 2011 6:55 PM > > To: Wan, Shuang > > Cc: meego...@meego.com > > Subject: RE: [Meego-qa] Default ass

Re: [Meego-qa] Default assignee "need-tri...@meego.com"

Hello Andre, > -Original Message- > From: Andre Klapper [mailto:aklap...@openismus.com] > Sent: Thursday, June 09, 2011 6:55 PM > To: Wan, Shuang > Cc: meego...@meego.com > Subject: RE: [Meego-qa] Default assignee "need-tri...@meego.com" > > Hi Shuang, > > On Thu, 2011-06-09 at 10:29 +08

Re: [Meego-qa] testset mapping list in qa report page - for review

Hello jarno please don't change names today. We have new proposal. Proposal will be sent on monday. Br, srikanth -Original Message- From: ext Jarno Keskikangas Sent: 09/06/2011, 12:45 To: Fu, Elva Cc: meego-qa@lists.meego.com Subject: Re: [Meego-qa] testset mapping list in qa report page

Re: [Meego-qa] Default assignee "need-tri...@meego.com"

Hi Shuang, On Thu, 2011-06-09 at 10:29 +0800, Wan, Shuang wrote: > > > > > Folks reassign tasks to this account with a comment in the spirit of "I > > > am not the right assignee and I don't care to find the right one" with > > > no follow-up process whatsoever that is known to me. > > The bugs

Re: [Meego-qa] Risk Level / UX Status fields [was: BoF MeeGo Bugzilla Structure Enhancement Prototype in SF conference - Meeting minutes]

Ping - no answer for a week, can somebody please answer this? andre On Thu, 2011-06-02 at 21:13 +0800, Zhao, Fan wrote: > https://bugs.meego.com/show_bug.cgi?id=3187 and feel free to discuss > with bugzilla experts in that bug entry. I see "Risk level" is set to Red for that ticket. As asked a

Re: [Meego-qa] testset mapping list in qa report page - for review

In case no further comments are received, we are changing the test set names according to Elva's proposal at the beginning of next week. Br, Jarno On 9 June 2011 04:47, Fu, Elva wrote: > > Use case testing for developer edition could be mapped to key feature > > (based on test set list options:

Re: [Meego-qa] How to apply log-in account for http://qa-reports.meego.com/? Thanks

Hi all, In order to get an account to QA Reports, please open a ticket as described in the documentation: http://wiki.meego.com/Quality/QA-tools/QAReports The registration up url should be kept confidential as all the signed-in users have all the rights in the system. For that reason, we want to

Re: [Meego-qa] Summary of EM BoF session at MeeGo Conf SF

Hi, I think that linking to all emails on meego-qa@ that provided summaries of San Francisco sessions from http://wiki.meego.com/Quality/meetings#Logs would make the most sense. Go ahead if you feel like, otherwise I might later today. :) andre On Thu, 2011-05-26 at 14:05 +0800, Fu, Elva wrote:

Re: [Meego-qa] BoF MeeGo Bugzilla Structure Enhancement Prototype in SF conference - Meeting minutes

On Thu, 2011-06-09 at 11:05 +0800, Zhao, Fan wrote: > I apologize if the terms confused you. To simplify, RESOLVED FIXED > means the fix is checked into git tree @ gitorious.org, while > SUBMITTED FIXED means the fix is submitted to OBS (MeeGo > distribution). Can you tell me which action do not ne

[Meego-qa] Meego Tablet Bug Triage Meeting Minutes - 20110609

#meego-meeting2: MeeGo Tablet Bug Triage Meeting Meeting started by dtao at 06:58:05 UTC (full logs). Meeting summary 1. Bug 18751 - Two modes for music playback needed: queue, and "now playing" (d