calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan <...@dankeeley.co.uk>
Subject Re: [DISCUSS] Email notifications for JIRA cases
Date Fri, 11 Mar 2016 21:48:28 GMT
+1

In my experience reading jira and tracking it is the single most effective
way to keep up to speed on a project.

It also highlights the ways people use the product.. often in ways
developers didn't envisage and that's where the fun comes in.

Dan

Sent from my phone
On 11 Mar 2016 20:56, "Julian Hyde" <jhyde@apache.org> wrote:

> I’d like to discuss the channels we use for notifying changes to JIRA
> cases. Currently[1], you will receive a notification for just about every
> change to a JIRA if you subscribe to issues@ (but only 18 people do)[2].
> You will also receive a notification if you are the reporter or assignee.
>
> I propose that when a JIRA is created, we send an email to both dev@ and
> issues@. This will be an extra 40 emails per month on the dev list. I am
> really cautious about increasing the number of messages on the dev list,
> because I think high-volume lists discourage part-time contributors, but I
> think this change is worthwhile. It will make people aware of conversations
> that are happening and if it helps to channel conversations onto JIRA cases
> it could possibly even REDUCE the volume on the dev list.
>
> Julian
>
> [1]
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> <
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> >
>
> [2] Email stats:
> * issues: 18 subscribers, 300 emails per month
> * commits: 18 subscribers, 140 emails per month
> * dev: 173 subscribers, 150 emails per month
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message