Hi May, > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Xie, May > Sent: Friday, June 10, 2011 3:32 PM > To: [email protected]; Clark, Joel; Zhao, Fan; Tao, Daniel; > [email protected] > Subject: Re: [Meego-qa] Filing bugs for MeeGo 1.2.1 release > > The discussion is clear to most of people. Since MeeGo update team is waiting > for the new version to kick off 1.2.0 update bug tracking, we need add 1.2.0 > to > bugzilla now. Shuang, would you please help on it?
Sure! I will do it soon. Regards Shuang > > Daniel has opened bug for it Bug 18860 - Add a new value "1.2.0" in MeeGo > Release field is reported to track this issue. Anyone who has better idea > could > continue the discussion in the bug directly. > > We will also publish 1.2.0/1.2.1 bug tracking process on wiki soon. Stay > tuned! > > May > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > [email protected] > > Sent: Friday, June 10, 2011 2:47 PM > > To: Clark, Joel; Zhao, Fan; Tao, Daniel; [email protected] > > Subject: 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 [[email protected]] > > Lähetetty: 10. kesäkuuta 2011 9:40 > > Vastaanottaja: Huttunen Iekku (EXT-Ixonos/Tampere); Zhao, Fan; Tao, Daniel; > > [email protected] > > Aihe: RE: 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 stuff leading to the > > 1.2.1 release. Bugs that are specifically intended to be fixed in 1.2.0 > > update > > should be clone/reported against 1.2.0. Bugs against 1.2 can be fixed there > > and released in 1.2.1 and if needed cloned and fixed in 1.2.0 update. > > > > regards > > Joel > > > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > [email protected] > > Sent: Thursday, June 09, 2011 10:54 PM > > To: Zhao, Fan; Tao, Daniel; [email protected] > > Subject: 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 > > release-mailing list. I'm not allowed to send mails to that mailing list, > > even I > > have asked permission to do that. I don't think that 1.2 is good for > > tracking > > the 1.2.1 bugs, since there's huge amount of existing 1.2 baseline bugs, I'm > > hoping to get fixed to the 1.2 update. > > > > Correct me if I have understood something wrong, but my understanding is > > that 1.2 update and 1.2.1 have different content. And 1.2.1 isn't really > > update > > for 1.2 but own branch? > > > > Br, > > Iekku > > ________________________________________ > > Lähettäjä: ext Zhao, Fan [[email protected]] > > Lähetetty: 10. kesäkuuta 2011 8:42 > > Vastaanottaja: Huttunen Iekku (EXT-Ixonos/Tampere); Tao, Daniel; > > [email protected] > > Aihe: RE: Filing bugs for MeeGo 1.2.1 release > > > > > Sent: Friday, June 10, 2011 1:27 PM > > > [email protected] 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 that much changes in Bugzilla's > > current > > > structure. > > > > I don't think so, 1.2.1 hasn't been released, how can people report bugs to > > 1.2.1 which is a not yet existing release? So the right thing to do is to > > keep 1.2 > > and track most bug fixes on 1.2 branch (after 9/1 we can rename 1.2 to 1.2.1 > > if necessary), while we can add 1.2.0 to clone bugs which we proposed to be > > fixed on 1.2.0 update branch to that release. The bugs which can be fixed on > > 1.2.0 update branch would be limited though, as 1.2.0 update branch is under > > CCB. > > > > > > > > Br, > > > Iekku > > > ________________________________________ > > > Lähettäjä: ext Tao, Daniel [[email protected]] > > > Lähetetty: 10. kesäkuuta 2011 8:22 > > > Vastaanottaja: Huttunen Iekku (EXT-Ixonos/Tampere); > > > [email protected] > > > Aihe: RE: 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: [email protected] > > > [mailto:[email protected]] On Behalf Of > > > [email protected] > > > Sent: Friday, June 10, 2011 1:06 PM > > > To: [email protected] > > > Subject: [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, I can > > > take > > > action to create the needed option. > > > > > > Br, > > > Iekku > > _______________________________________________ > > 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 > _______________________________________________ > 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
