On Tue, Nov 23, 2010 at 9:31 AM, Marko Saukko <[email protected]> wrote: > On 11/22/2010 11:01 PM, Alexander Kanevskiy wrote: >> >> On Mon, Nov 22, 2010 at 6:26 PM, Anas Nashif<[email protected]> >> wrote: >>> >>> On 2010-11-22, at 3:46 PM, Alexander Kanevskiy wrote: >>> >>> Why not create an umbrella bug for this? We might also need to consider >>> revisit the idea of adding all packages as components, at least in the >>> "Build System" product, then it will be easy to automate this :) >> >> I would prefer first to see re-structured Bugzilla plus mapping all >> packages to architecture domains/components with assigned >> maintainership. >> Until we get clear understanding where in hierarchy package belongs >> and who is responsible for it, every other solution would be a dirty >> workarround :( >> > > Do you mean that not file a bugs at all currently about this?
No, it's side track discussion that we going for some time already with Anas about how to organize package metadata in a way that it would be easy for people and scripts to file bugs about packages. >>>>> Then comes the question to which component? Some of these packages do >>>>> not >>>>> have their own component so would it be then "MeeGo OS Base / Others" >>>>> for >>>>> example? >>>>> > > So do we have any place currently to place these bugs for these individual > packages? Also do we have an list of package maintainers of packages > somewhere were the rightful bug owner could be seen? Or do we just pick > person with most commits to certain package to the assignee if there isn't > suitable product for the package? We have components in Bugzilla, but it's not always trivial to find correct one. Usually it's best guess, and if guess was wrong, after couple of bounces bug riches correct owner :) -- br, Alexander Kanevskiy _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
