> 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
