I've seen the page yesterday and I must say it's an excellent idea!
Cheers,
S
8/16/05, Trygve Laugstl <trygvis (AT) codehaus (DOT) orgwrote:
Hi!
I've added a field to our JIRA instance called "Complexity". This field is
an indicator on how hard the issue will be, for the actual definition,
please read[1]. There's a wiki page at our Codehaus Confluence that reads
from JIRA and shows an updated list[2].
The intention is to make it easier for new folks that would like to help
out on Maven development.
Please try to set the field if you feel that it something a non-committer
should be able to solve.
[1]:
[2]:

remark though. I think the Jira's filters should be updated to
take only "Unassigned" issues. If the issue is currently assigned, we
could assume someone is taking care of it, right?

WDYT?

Cheers,
S

8/17/05, Stephane Nicoll <stephane.nicoll (AT) gmail (DOT) comwrote:
I've seen the page yesterday and I must say it's an excellent idea!

Cheers,
S

8/16/05, Trygve Laugstl <trygvis (AT) codehaus (DOT) orgwrote:
Hi!

I've added a field to our JIRA instance called "Complexity". This field is
an indicator on how hard the issue will be, for the actual definition,
please read[1]. There's a wiki page at our Codehaus Confluence that reads
from JIRA and shows an updated list[2].

The intention is to make it easier for new folks that would like to help
out on Maven development.

Please try to set the field if you feel that it something a non-committer
should be able to solve.

[1]:
[2]:

Be careful with this rule
A lot of plugins (in m1) are auto-assigned to the plugin's manager.
I must deactivate this rules for my plugins but I always forgot to do it
Actually I have more than one hundred of issues assigned to me.
I know that Jason had also a lot of issues.

Arnaud

8/22/05, Trygve Laugstl <trygvis (AT) codehaus (DOT) orgwrote:

Mon, Aug 22, 2005 at 12:15:59PM +0200, Stephane Nicoll wrote:
remark though. I think the Jira's filters should be updated to
take only "Unassigned" issues. If the issue is currently assigned, we
could assume someone is taking care of it, right?

WDYT?

Hm, that's a good point. Unless someone objects to this I'll do it later
today.

Yes I think it's not a good practice to assign by default the issue to
someone.
The person shhould assign it to himself when he wants to work on it.
I just removed the default assignement for my plugin in m1 ;-)

Arnaud

8/22/05, Trygve Laugstl <trygvis (AT) codehaus (DOT) orgwrote:

Mon, Aug 22, 2005 at 12:37:37PM +0200, Arnaud HERITIER wrote:
Be careful with this rule
A lot of plugins (in m1) are auto-assigned to the plugin's manager.
I must deactivate this rules for my plugins but I always forgot to do it
Actually I have more than one hundred of issues assigned to me.
I know that Jason had also a lot of issues.

The lists are currently only for Maven 2 issues but there is no reason why
they shouldn't cover Maven 1 issues in the future.

IM there shouldn't be a default assignee, WDYT?

Yes sorryyyyyyyyyyyyy
I didn't think to the email notification !!! :-(

Arnaud

8/22/05, Trygve Laugstl <trygvis (AT) codehaus (DOT) orgwrote:

Mon, Aug 22, 2005 at 01:41:40PM +0200, Arnaud HERITIER wrote:
Yes I think it's not a good practice to assign by default the issue to
someone.
The person shhould assign it to himself when he wants to work on it.
I just removed the default assignement for my plugin in m1 ;-)

Yah, noticed that, cinda hard to miss :) In the future we can temporarily
disable notifications instead of sending out tons of emails and just send
out a status mail afterwards.