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:

On Mon, Nov 22, 2010 at 5:27 PM, Marko Saukko<[email protected]>  wrote:
Hi,

I did an image with --excludedocs in the %packages section of .ks and got
following errors. I was wondering that should these be fixed? Because all
submit requests needs to have bug number all these should be reported as
separate bugs if they should be fixed?

yes, in that particular scenario - one bug per package.


Overkill :)

Nope. Packages are maintained by different people. bug per package in
that scenario would add TODO items into package owner lists.
Also, it's easier to track that way, so if some package would be fixed
incorrectly and all others are fine, it would be only particular bug
reopened during verification. In other scenario (one bug for all
packages)  QA would not need to review again dozen of packages while
it was only one fixed incorrectly.


I agree that the one bug per package would be easiest way to trac the bug. It seems a bit overkill but well ID numbers from bugzilla are not ending very soon ;)

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?


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?

Regards,
Marko

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to