JIRA <-> dev list not in sync?

[Thomas Bernhard <tb...@yahoo.com>]

It looks like JIRA and the dev lists are not in sync.
E.g. many comments to JIRA issues won't be displayed on the dev list (and
unless people apply for "watch issue" than comments might slip unobserved).

I'm not sure on what criteria this happens: just saw that some of my isues
got
comments, but weren't diplayed on the dev list - but may other issues have
comments on the dev list too.

Thanx,
Tom.
-- 
View this message in context: http://www.nabble.com/JIRA-%3C-%3E-dev-list-not-in-sync--tf4678583.html#a13367849
Sent from the Cayenne - Dev mailing list archive at Nabble.com.

Re: JIRA <-> dev list not in sync?

[Andrus Adamchik <an...@objectstyle.org>]

Done

On Oct 23, 2007, at 8:01 PM, Kevin Menard wrote:

> +1 for sending more to the dev list.
>
> --  
> Kevin
>
>
> On 10/23/07 12:45 PM, "Andrus Adamchik" <an...@objectstyle.org>  
> wrote:
>
>>
>> On Oct 23, 2007, at 7:34 PM, Mike Kienenberger wrote:
>>
>>> The decision to only send newly-created JIRA issue to the dev  
>>> mailing
>>> list was intentional,
>>
>> Correct.
>>
>>> but I've been thinking about bringing it up
>>> again for the last week.
>>>
>>> I'd like to see things set up so that all updates to JIRA issues are
>>> posted to the dev list by default.   This is how it's done in the
>>> other Apache projects I've participated in (struts, MyFaces, Shale,
>>> Velocity).
>>
>> I can expand the list notifications to include "Issue Commented",
>> "Issue Resolved", "Issue Closed" and "Issue Reopened" events if
>> nobody objects. This still leaves a possibility of communication
>> breakage: when a dev list subscriber replies to a jira email, the
>> issue author will not see the reply if (s)he is not subscribed to the
>> list. But that's still better than what we have.
>>
>> Also aside from "close" notifications, we shouldn't get much extra
>> traffic, as only a small subset of issues generate long comment  
>> threads.
>>
>> So unless there are objections, I'll make this change.
>>
>> Andrus
>
>

Re: JIRA <-> dev list not in sync?

[Kevin Menard <km...@servprise.com>]

+1 for sending more to the dev list.

-- 
Kevin


On 10/23/07 12:45 PM, "Andrus Adamchik" <an...@objectstyle.org> wrote:

> 
> On Oct 23, 2007, at 7:34 PM, Mike Kienenberger wrote:
> 
>> The decision to only send newly-created JIRA issue to the dev mailing
>> list was intentional,
> 
> Correct.
> 
>> but I've been thinking about bringing it up
>> again for the last week.
>> 
>> I'd like to see things set up so that all updates to JIRA issues are
>> posted to the dev list by default.   This is how it's done in the
>> other Apache projects I've participated in (struts, MyFaces, Shale,
>> Velocity).
> 
> I can expand the list notifications to include "Issue Commented",
> "Issue Resolved", "Issue Closed" and "Issue Reopened" events if
> nobody objects. This still leaves a possibility of communication
> breakage: when a dev list subscriber replies to a jira email, the
> issue author will not see the reply if (s)he is not subscribed to the
> list. But that's still better than what we have.
> 
> Also aside from "close" notifications, we shouldn't get much extra
> traffic, as only a small subset of issues generate long comment threads.
> 
> So unless there are objections, I'll make this change.
> 
> Andrus

Re: JIRA <-> dev list not in sync?

[Andrus Adamchik <an...@objectstyle.org>]

On Oct 23, 2007, at 7:34 PM, Mike Kienenberger wrote:

> The decision to only send newly-created JIRA issue to the dev mailing
> list was intentional,

Correct.

> but I've been thinking about bringing it up
> again for the last week.
>
> I'd like to see things set up so that all updates to JIRA issues are
> posted to the dev list by default.   This is how it's done in the
> other Apache projects I've participated in (struts, MyFaces, Shale,
> Velocity).

I can expand the list notifications to include "Issue Commented",  
"Issue Resolved", "Issue Closed" and "Issue Reopened" events if  
nobody objects. This still leaves a possibility of communication  
breakage: when a dev list subscriber replies to a jira email, the  
issue author will not see the reply if (s)he is not subscribed to the  
list. But that's still better than what we have.

Also aside from "close" notifications, we shouldn't get much extra  
traffic, as only a small subset of issues generate long comment threads.

So unless there are objections, I'll make this change.

Andrus

Re: JIRA <-> dev list not in sync?

[Mike Kienenberger <mk...@gmail.com>]

The decision to only send newly-created JIRA issue to the dev mailing
list was intentional, but I've been thinking about bringing it up
again for the last week.

I'd like to see things set up so that all updates to JIRA issues are
posted to the dev list by default.   This is how it's done in the
other Apache projects I've participated in (struts, MyFaces, Shale,
Velocity).

Failing that, I'd like to at least have the ability to subscribe to a
mailing list where they are posted automatically.  Maybe this is
already possible and I've simply overlooked how to do it.

On 10/23/07, Thomas Bernhard <tb...@yahoo.com> wrote:
>
> It looks like JIRA and the dev lists are not in sync.
> E.g. many comments to JIRA issues won't be displayed on the dev list (and
> unless people apply for "watch issue" than comments might slip unobserved).
>
> I'm not sure on what criteria this happens: just saw that some of my isues
> got
> comments, but weren't diplayed on the dev list - but may other issues have
> comments on the dev list too.
>
> Thanx,
> Tom.
> --
> View this message in context: http://www.nabble.com/JIRA-%3C-%3E-dev-list-not-in-sync--tf4678583.html#a13367849
> Sent from the Cayenne - Dev mailing list archive at Nabble.com.
>
>