Re: Setup of a issues@flink.incubator.a.o mailing list

Posted by Ted Dunning on
URL: http://deprecated-apache-flink-mailing-list-archive.368.s1.nabble.com/Setup-of-a-issues-flink-incubator-a-o-mailing-list-tp35p52.html

JIRA can also be reconfigured to send only to dev@ on create.




On Wed, Jun 11, 2014 at 4:08 PM, Sean Owen <[hidden email]> wrote:

> I think it is helpful to separate automated test / commit
> notifications into a separate list, separate from even dev and user.
> Especially if there is no dev list, it's essential. I like issues@
> myself as a place for automated notifications of all kinds. Later,
> consider a dev@ list if it's clear there is a lot of traffic that is
> not really user-relevant.
>
> On Wed, Jun 11, 2014 at 5:27 PM, Robert Metzger <[hidden email]>
> wrote:
> > Hi,
> >
> > I wanted to ask if we should set up a [hidden email] list?
> > It seems that JIRA is sending emails for every activity. And I think our
> > activity in JIRA is pretty low currently, so the traffic is probably
> going
> > up in the future.
> >
> > Since we do not have a separate users@ and dev@ mailing list, I don't
> want
> > to scare away users that are just subscribed for support or because they
> > are interested.
> > Or would it be more common to send the JIRA mails to [hidden email]
> ?
> >
> > What do you think?
> >
> > Robert
>