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 
release, we can add 1.2.1 to track 1.2.1 update bugs. If no 1.2.2 or later 
release, we can change 1.2 to 1.2.1 for 1.2.1 update bugs or keep unchange;

2)       Add 1.2.1 to track 1.2.1 bugs and keep 1.2 to track 1.2.0 update bugs. 
After 1.2.1 is released, if we will continue to have 1.2.2 or later release, we 
can add 1.2.1 to track 1.2.2 release. If no 1.2.2 or later release, we can keep 
1.2.1 to track 1.2.1 update and 1.2 to track 1.2.0 update.

Both solutions look similar and the concern is that which kind of change does 
make sense for community user and they can understand it easily.

Thanks

Daniel

From: [email protected] [mailto:[email protected]]
Sent: Friday, June 10, 2011 1:27 PM
To: Tao, Daniel; [email protected]
Subject: VS: 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
________________________________
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

Reply via email to