Hi, the tracker allows categories (of course). What do you thing about creating a category for each module, other for core and some other called "other"?
Hello,
On 06/10/2009 05:04 PM, Iñaki Baz Castillo wrote:
Hi, the tracker allows categories (of course). What do you thing about creating a category for each module, other for core and some other called "other"?
I think is too much to have one for each module -- there are over 100 modules. Maybe tm could be separate, otherwise, a single category "Modules" with appropriate module name in summary should be ok.
Cheers, Daniel
2009/6/10 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
On 06/10/2009 05:04 PM, Iñaki Baz Castillo wrote:
Hi, the tracker allows categories (of course). What do you thing about creating a category for each module, other for core and some other called "other"?
I think is too much to have one for each module -- there are over 100 modules. Maybe tm could be separate, otherwise, a single category "Modules" with appropriate module name in summary should be ok.
Yes, I agree, but under my experience in Kamailio/OpenSer sourceforge tracker, most of the bugs related to modules don't include the module name in the summary :(
Anyway I agree with you, 100 categories would be too much.
Agreed that a catagory for each module is not a practical approach....
And what about categories like: - compilation; - script; - parameter; - run-time; - etc, etc, etc
at least it would permit filter problems by 'moment'...
Edson.
Iñaki Baz Castillo escreveu:
2009/6/10 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
On 06/10/2009 05:04 PM, Iñaki Baz Castillo wrote:
Hi, the tracker allows categories (of course). What do you thing about creating a category for each module, other for core and some other called "other"?
I think is too much to have one for each module -- there are over 100 modules. Maybe tm could be separate, otherwise, a single category "Modules" with appropriate module name in summary should be ok.
Yes, I agree, but under my experience in Kamailio/OpenSer sourceforge tracker, most of the bugs related to modules don't include the module name in the summary :(
Anyway I agree with you, 100 categories would be too much.
Just notice that, using anonymous access, there are only "linux" and "mac" as OS options.
Shouldn't include Solaris/Open Solaris?
Edson.
Edson - Lists escreveu:
Agreed that a catagory for each module is not a practical approach....
And what about categories like:
- compilation;
- script;
- parameter;
- run-time;
- etc, etc, etc
at least it would permit filter problems by 'moment'...
Edson.
Iñaki Baz Castillo escreveu:
2009/6/10 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
On 06/10/2009 05:04 PM, Iñaki Baz Castillo wrote:
Hi, the tracker allows categories (of course). What do you thing about creating a category for each module, other for core and some other called "other"?
I think is too much to have one for each module -- there are over 100 modules. Maybe tm could be separate, otherwise, a single category "Modules" with appropriate module name in summary should be ok.
Yes, I agree, but under my experience in Kamailio/OpenSer sourceforge tracker, most of the bugs related to modules don't include the module name in the summary :(
Anyway I agree with you, 100 categories would be too much.
2009/6/10 Edson - Lists 4lists@gmail.com:
Agreed that a catagory for each module is not a practical approach....
And what about categories like:
- compilation;
- script;
- parameter;
- run-time;
- etc, etc, etc
at least it would permit filter problems by 'moment'...
Sincerelly I wouldn't know which of the above categories I should choose for most of the bugs I've reported XD
IMHO it should be really simpler.
On Wed, June 10, 2009 5:35 pm, Iñaki Baz Castillo wrote:
I think is too much to have one for each module -- there are over 100 modules. Maybe tm could be separate, otherwise, a single category "Modules" with appropriate module name in summary should be ok.
Yes, I agree, but under my experience in Kamailio/OpenSer sourceforge tracker, most of the bugs related to modules don't include the module name in the summary :(
Hi Inaki,
well, this should be rather easy to fix, even if its forgotten from the original reporter. ;-) At least as an admin it should be possible to edit the summary.
Henning
2009/6/10 Henning Westerholt henning.westerholt@1und1.de:
On Wed, June 10, 2009 5:35 pm, Iñaki Baz Castillo wrote:
I think is too much to have one for each module -- there are over 100 modules. Maybe tm could be separate, otherwise, a single category "Modules" with appropriate module name in summary should be ok.
Yes, I agree, but under my experience in Kamailio/OpenSer sourceforge tracker, most of the bugs related to modules don't include the module name in the summary :(
Hi Inaki,
well, this should be rather easy to fix, even if its forgotten from the original reporter. ;-) At least as an admin it should be possible to edit the summary.
Right, this would be the best approach :)
On 10-06 16:04, Iñaki Baz Castillo wrote:
Hi, the tracker allows categories (of course). What do you thing about creating a category for each module, other for core and some other called "other"?
Is it necessary to create them now? We can add categories on the fly as needed, also depending on the amount of bug reports received.
Jan.
-
Daniel-Constantin Mierla -
Edson - Lists -
Henning Westerholt -
Iñaki Baz Castillo -
Jan Janak