Hi, That is a good question.
I agree, that bugs should be fixed in MeeGo and not just in CE. However, lately the problem has been that MeeGo 1.3 has obsoleted Handset UX and it also looks like 1.2 branch is not really accepting fixes to Handset apps. For example the bug about SMS and VKB: https://bugs.meego.com/show_bug.cgi?id=15407 Clearly this is major annoyance as VKB overlapps input field (you cannot see what you are typing). Despite this being major issue we did not get MeeGo_Release_Blocker flag for it (and no comment why). Therefore the fix cannot go to 1.2 despite it being relatively small patch and just to the SMS app. So I did a MR to upstream: https://meego.gitorious.org/meego-handset-ux/meego-handset-sms/merge_requests/2 and that hasn't landed either. Also we have one MR for bug fix that hasn't landed in two months. As SMS app upstream has not changed after May 12th, it looks dead. This issue is same with many other handset apps. So the question is that does it make sense to keep Handset UX issues open in MeeGo bugzilla, after we have fixed in issue in CE? If there was a good change of getting the fixes in, I would definitely keep the bugs open until they are fixed in 1.2.x, but as the Handset UX seems stalled/dead, I do not know what would be good way of handling these. BR, Vesku On 17.8.2011, at 4:44, ext Luis Araujo wrote: > Hello, > > A N900 bug should be resolved as fixed if such a bug is fixed for the N900CE > version? > > I have seen some bugs following this trend, and I am not sure if this is what > we want, or if this was discussed somewhere, do we have a consensus about how > to go in such a situation where one bug is fixed in one version but not in > other? > > In my opinion a N900 bug should stay open as long as it is reproduced in the > vanilla images, or, if Release Managers decide to mark as INVALID or WONTFIX > for such a version. Now, I agree that a N900 bug could be used to track > N900CE issues too, but closing a bug reported for one image version, because > it is fixed in another image version is a bit confusing in my opinion, even > if it is platform related. > > Comments?, I am not sure if this is explained somewhere, but it'd be nice if > we could get a consensus about this if there is none yet. > > Regards, > _______________________________________________ > MeeGo-handset mailing list > MeeGo-handset@lists.meego.com > http://lists.meego.com/listinfo/meego-handset _______________________________________________ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
