Hi, there, Could anybody pls. response to the questions from Iekku and Qingqing? And also pls. kindly clarified why we make this change and what's the benefit of it.
Best Regards, Jason > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Monday, June 13, 2011 4:26 PM > To: [email protected]; [email protected]; > [email protected]; [email protected] > Subject: Re: [Meego-qa] [meego-releases] Release Engineering Update on Bug > Status Changes > > Hi, > > Good question. I also wonder how we can separate the verified in trunk:testing > and verified in daily/weekly image. And how we can know that bug fix is in the > daily/weekly image, after verified in trunk:testing. > > Br, > Iekku > > >-----Original Message----- > >From: [email protected] [mailto:meego-releases- > >[email protected]] On Behalf Of ext [email protected] > >Sent: 13 June, 2011 10:10 > >To: [email protected]; [email protected]; meego- > >[email protected]; [email protected] > >Subject: Re: [meego-releases] [Meego-qa] Release Engineering Update on > >Bug Status Changes > > > >Hi, > > > >Thanks for the update. > > > >One question, based on the new process, "trunk: testing" image be used > >to verify the "RELEASED" bug, does the "RELEASED" bug still need to be > >verified again with "trunk" image after the fix is promoted to trunk? > >The point is we shall guarantee the fixed/implemented bug/feature is > >also working properly in the trunk image/weekly image but also avoiding > >overlap work. > > > >Br, > >-Tu > >________________________________ > > > > From: [email protected] > >[mailto:[email protected]] On Behalf Of Ulf Hofemeier > > Sent: 11 June 2011 00:27 > > To: [email protected]; Collaboration list for Release > >Engineering and QA teams (moderateddiscussion list); > >[email protected] list) > > Subject: [Meego-qa] Release Engineering Update on Bug Status > >Changes > > > > > > Hello, > > > > Release Engineering and QA have agreed on a proposal that will > >introduce a minor change to the way bug status updates for package > >acceptance into MeeGo repositories will be handled. > > > > Previously R.E. set bugs to 'released' only when packages were > >promoted to Trunk. Following up, QA verified that the bug/feature was > >fixed properly and set the bug status to 'verified'. > > > > Old: Marked as 'resolved' by developer -> submitted to > >Trunk:Testing -> accepted by R.E. -> promoted to Trunk -> marked as > >'released' by R.E. > > > > The new process is for R.E. to set the status of a bug to > >'released' once the package is in Trunk:Testing and not wait until it > >has been promoted to Trunk. > > > > New: Marked as 'resolved' by developer -> submitted to > >Trunk:Testing -> accepted by R.E.-> marked as 'released' by R.E once the > >package is in Trunk:Testing. > > > > What this means is that QA will focus on Trunk:Testing images > >and look for 'released' bugs that have been accepted into Trunk:Testing > >and validate that the bug/feature was fixed/implemented before the > >package will be promoted to Trunk. > > > > Thanks, > > > > Release Engineering > > > > > > > > > >_______________________________________________ > >MeeGo-releases mailing list > >[email protected] > >http://lists.meego.com/listinfo/meego-releases > _______________________________________________ > MeeGo-qa mailing list > [email protected] > http://lists.meego.com/listinfo/meego-qa _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
