You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2009/04/17 12:20:23 UTC
Jira notifications (Was: [jira] Commented: (JCRRMI-21) RMI: Unable to
register NodeTypes)
Hi,
On Fri, Apr 17, 2009 at 12:08 PM, Torgeir Veimo <to...@pobox.com> wrote:
> Is there any chance the jira messages could go on the commit mailing list?
That's possible, though see below.
> I assume those how follow the commit list would amount to the same people
> that are interested in jira issues mails?
On the other hand, I would assume that everyone on dev@ would be
interested in the Jira issues, as that's where much of the development
discussion occurs.
The way I see it, dev@ is for things that should happen and commits@
is for things that actually did happen with our codebase (and web
site). As such, Jira notifications IMHO belong on dev@.
That's just me though, so if enough people disagree then we can of
course change the Jira settings.
BR,
Jukka Zitting
Re: Jira notifications (Was: [jira] Commented: (JCRRMI-21) RMI:
Unable to register NodeTypes)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Apr 17, 2009 at 12:23 PM, Torgeir Veimo <to...@pobox.com> wrote:
> True, but it's both informal and formal development discussions on the list.
> Jira messages goes in the second category. I merely follow the informal
> discussions.
Some Apache projects have a separate issues@ list where notifications
from issue trackers are sent. If there's enough demand we could do
something like that.
Alternatively, you could simply filter out all messages from jira@apache.org.
BR,
Jukka Zitting
Re: Jira notifications (Was: [jira] Commented: (JCRRMI-21) RMI:
Unable to register NodeTypes)
Posted by Torgeir Veimo <to...@pobox.com>.
True, but it's both informal and formal development discussions on the list.
Jira messages goes in the second category. I merely follow the informal
discussions.
2009/4/17 Jukka Zitting <ju...@gmail.com>
> Hi,
>
> On Fri, Apr 17, 2009 at 12:08 PM, Torgeir Veimo <to...@pobox.com> wrote:
> > Is there any chance the jira messages could go on the commit mailing
> list?
>
> That's possible, though see below.
>
> > I assume those how follow the commit list would amount to the same people
> > that are interested in jira issues mails?
>
> On the other hand, I would assume that everyone on dev@ would be
> interested in the Jira issues, as that's where much of the development
> discussion occurs.
>
> The way I see it, dev@ is for things that should happen and commits@
> is for things that actually did happen with our codebase (and web
> site). As such, Jira notifications IMHO belong on dev@.
>
> That's just me though, so if enough people disagree then we can of
> course change the Jira settings.
>
> BR,
>
> Jukka Zitting
>
--
-Tor
Re: Jira notifications (Was: [jira] Commented: (JCRRMI-21) RMI:
Unable to register NodeTypes)
Posted by Alexander Klimetschek <ak...@day.com>.
On Fri, Apr 17, 2009 at 12:20 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Apr 17, 2009 at 12:08 PM, Torgeir Veimo <to...@pobox.com> wrote:
>> Is there any chance the jira messages could go on the commit mailing list?
>
> That's possible, though see below.
>
>> I assume those how follow the commit list would amount to the same people
>> that are interested in jira issues mails?
>
> On the other hand, I would assume that everyone on dev@ would be
> interested in the Jira issues, as that's where much of the development
> discussion occurs.
>
> The way I see it, dev@ is for things that should happen and commits@
> is for things that actually did happen with our codebase (and web
> site). As such, Jira notifications IMHO belong on dev@.
ACK. Please keep the Jira messages on dev@. As you noted, the rest is
filtering (Clay Shirky: "It's Not Information Overload. It's Filter
Failure.").
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com