bugs.kde.org product/component for plugins

[Sven Brauch]

I'm not sure whether it makes sense to have an extra component for
each of the "small" plugins... maybe just create
kdevelop-plugins-others or kdevelop-plugins-extra or so?
Since the language support plugins are likely to have way more bug
reports than e.g. the upload or executescript plugin it might be
useful to have an extra component for them, but not for the others.

There's also those sub-products (or components or what it's called),
couldn't a component be created for each plugin then? That would
probably be fine-grained enough, no?

Cheers,
Sven

2012/11/10 Niko Sams <niko.sams at gmail.com>:
> Hi,
>
> where should users report bugs for plugins like kdev-upload,
> kdev-xdebug and so on?
> - kdev-python has it's own product
> - there was a upload/xdebug component in quanta (but quanta is not
> open for new bugs and it's confusing anyway)
> - php has it's own component in kdevelop (well actually two)
>
> How do we want to handle this?
>
> cheers,
> Niko
>
> PS: I have bugzilla permissions to change products
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel