hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Gates <ga...@hortonworks.com>
Subject Re: Propose to put JIRA traffic on separate hive list
Date Fri, 21 Nov 2014 20:59:16 GMT
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.

> Sergey Shelukhin <mailto:sergey@hortonworks.com>
> November 18, 2014 at 13:34
> +1
>
> On Tue, Nov 18, 2014 at 2:12 AM, Lars Francke <lars.francke@gmail.com>
>
> Lars Francke <mailto:lars.francke@gmail.com>
> November 18, 2014 at 2:12
> +1
>
> That's a great idea Alan.
>
> On Tue, Nov 18, 2014 at 9:49 AM, Lefty Leverenz <leftyleverenz@gmail.com>
>
> Lefty Leverenz <mailto:leftyleverenz@gmail.com>
> November 18, 2014 at 0:49
> +1
>
> Would it be possible to send commits to the dev list, as well as creates?
> Or maybe all changes to the Resolution or Status?
>
> -- Lefty
>
>
> Alan Gates <mailto:gates@hortonworks.com>
> November 17, 2014 at 14:27
> The hive dev list generates a lot of traffic.  The average for October 
> was 192 messages per day.  As a result no one sends hive dev directly 
> to their inbox.  They either unsubscribe or they build filters that 
> ship most or all of it to a folder.  Chasing people off the dev list 
> is obviously not what we want.  Sending messages to folders means 
> missing messages or not seeing them until you get unbusy enough to go 
> read back mail in folders.
>
> The vast majority of this traffic is comments on JIRA tickets.  The 
> way I've seen other very active Apache projects manage this is JIRA 
> creates go to the dev list, but all other JIRA operations go to a 
> separate list.  Then everyone can see new tickets, and if they are 
> interested they can watch that JIRA.  If not, they are not burdened 
> with the email from it.
>
> I propose we do this same thing in Hive.
>
> 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.

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