Sorry I was unclear. Today RB traffic goes to the dev list. I'd like that
mail to not go to the dev list, thus reducing traffic.

On Fri, Nov 21, 2014 at 5:16 PM, Alan Gates <ga...@hortonworks.com> wrote:

> Do you mean RB creation?  I wouldn't be in favor of sending all RB
> activity to it, since we're trying to create a low traffic list.
>
> Alan.
>
>   Brock Noland <br...@cloudera.com>
>  November 21, 2014 at 17:10
> I think that RB activity could be put on this same list?
>
>
>   Brock Noland <br...@cloudera.com>
>  November 21, 2014 at 17:09
> +1
>
>
>   Szehon Ho <sze...@cloudera.com>
>  November 21, 2014 at 17:03
> +1. Create + resolve might be a good idea too, as I imagine contributors
> might want to see what is changing in Hive, and not just issues created.
>
> Thanks,
> Szehon
>
> On Fri, Nov 21, 2014 at 1:15 PM, Prasanth Jayachandran <
>
>   Prasanth Jayachandran <pjayachand...@hortonworks.com>
>  November 21, 2014 at 13:15
> +1
>
>
> - Prasanth
>
>   Alan Gates <ga...@hortonworks.com>
>  November 21, 2014 at 12:59
>  Poke, I got some scattered +1s but I'd like to get feedback from a higher
> percentage of committers before filing the infra ticket to do this.  Or
> maybe a better way to put it is, is anyone opposed?
>
> Lefty, to answer your question, we could include resolutions as well.  But
> that doubles the traffic going to the dev list.  I get why you're concerned
> with it, since resolutions are more important to you than creations.  I'm
> happy to help you set up a filter on the list with the non-creation JIRA
> traffic so you can just see the resolutions.
>
> Alan.
>
>
>
> --
> Sent with Postbox <http://www.getpostbox.com>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to