Hi, On 6/29/11 11:33 AM, "ext Zhao, Fan" <fan.z...@intel.com> wrote:
>> Wednesday, June 29, 2011 4:15 PM >> Marius Vollmer wrote: >> >> "ext Zhao, Fan" <fan.z...@intel.com> writes: >> >> >> Wednesday, June 29, 2011 3:13 PM >> >> Marius Vollmer wrote: >> >> >> >> "ext Zhao, Fan" <fan.z...@intel.com> writes: >> >> >> >> > The purpose of the "MeeGo Distribution Packages" product is to >>provide >> >> > an option for people to report/triage bugs to packages, and it's >>setup >> >> > for 1.3 bug reporting at this moment. >> >> >> >> Creating a new product is nice, but it is different from moving >>existing >> >> bugs into it en masse. This mass moving was not announced, as far >>as I >> >> can see. It is impolite to massively move bugs around without >> >> cooperating with the 'owners' of those bugs. >> >> >> >> Or maybe I misunderstand. In any case, the direction is right, so >>maybe >> >> we can live with some bumps on the way. >> > >> > Mass movement of bugs is not expected at this moment. >> >> So why is Michael saying the following then: >> >> I wondered why bugs for our component, the virtual keyboard, were >> moved to newly created components without prior announcement, nor >> explanations. >> >> Here is an example of a bug that was moved without a comment: >> >> https://bugs.meego.com/show_activity.cgi?id=15554 >> >> Anyway, none of my business, so I shut up. :) > >I just did a search, around 15 VKB bugs were moved to the new product, so >I don't think it's mass movement. If there are problems for that >component, let's solve the specific problem, but let's not overshade the >general direction. The point here isn't about the administrative task of moving bugs with the "change several bugs at once" bugzilla feature but making sure that an appropriate comment is attached to the bugs. So I guess you could remind anyone on your side involved into moving the bugs that it's mandatory to at least put a comment with the reasoning behind the action. In this case, yanshuang.zh...@intel.com needs to be reminded. Doing so will generate an email notification to anyone having incentive on the bug. Of course, announcements on the ML are good but as we all know, it's simply not enough as Michael and Marius point out... > >Thanks for bringing it up anyway. Another point is that one could actually challenge why some bugs were moved there if the purpose is to monitor 1.3 release. IMHO anything done already doesn't need to move, does it? Just verified and closed is largely enough. > >Thanks, >Fan Cheers, Eric >_______________________________________________ >MeeGo-dev mailing list >MeeGo-dev@meego.com >http://lists.meego.com/listinfo/meego-dev >http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
