Move Issues to a Different Mailing List

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Move Issues to a Different Mailing List

sirinath
Is it possible to move issues and PR related mail into a separate mailing list.
Reply | Threaded
Open this post in threaded view
|

Re: Move Issues to a Different Mailing List

Ryan Blue
On 04/09/2015 07:57 AM, sirinath wrote:
> Is it possible to move issues and PR related mail into a separate mailing
> list.
>
>
>
> --
> View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Move-Issues-to-a-Different-Mailing-List-tp1121.html
> Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.
>

Some projects have a commits@ list, but I think it's important to have
the pull requests and JIRA discussions available to the dev@ list
because a lot of the discussion that would traditionally happen on the
dev list happens in the issue tracker. To keep the community aware, I
think having those feed the dev list is a good idea.

Could you add a filter for the messages you don't want to see? It should
be pretty easy to set one up to catch "[GitHub]" in the subject or catch
the JIRA e-mail address. In fact, I don't see the JIRA updates getting
sent to this list, unless I've set up some rule to put them elsewhere
myself.

rb

--
Ryan Blue
Software Engineer
Cloudera, Inc.
Reply | Threaded
Open this post in threaded view
|

Re: Move Issues to a Different Mailing List

Joe Witt
Hello Sirinath,

I believe our automated messages from Git and from Jira already go to
our 'commits' distro only.  You can safely ignore those if staying up
to date with code and ticket activity via that mechanism isn't
desirable.

Are there emails to the dev list you're thinking of?

Thanks
JOe

On Thu, Apr 9, 2015 at 4:08 PM, Ryan Blue <[hidden email]> wrote:

> On 04/09/2015 07:57 AM, sirinath wrote:
>>
>> Is it possible to move issues and PR related mail into a separate mailing
>> list.
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Move-Issues-to-a-Different-Mailing-List-tp1121.html
>> Sent from the Apache NiFi (incubating) Developer List mailing list archive
>> at Nabble.com.
>>
>
> Some projects have a commits@ list, but I think it's important to have the
> pull requests and JIRA discussions available to the dev@ list because a lot
> of the discussion that would traditionally happen on the dev list happens in
> the issue tracker. To keep the community aware, I think having those feed
> the dev list is a good idea.
>
> Could you add a filter for the messages you don't want to see? It should be
> pretty easy to set one up to catch "[GitHub]" in the subject or catch the
> JIRA e-mail address. In fact, I don't see the JIRA updates getting sent to
> this list, unless I've set up some rule to put them elsewhere myself.
>
> rb
>
> --
> Ryan Blue
> Software Engineer
> Cloudera, Inc.