JIRA. github and asf updates

2014-03-29 Thread Mridul Muralidharan
Hi,

  So we are now receiving updates from three sources for each change to the PR.
While each of them handles a corner case which others might miss,
would be great if we could minimize the volume of duplicated
communication.


Regards,
Mridul


Re: JIRA. github and asf updates

2014-03-29 Thread Patrick Wendell
Mridul,

You can unsubscribe yourself from any of these sources, right?

- Patrick


On Sat, Mar 29, 2014 at 11:05 AM, Mridul Muralidharan mri...@gmail.comwrote:

 Hi,

   So we are now receiving updates from three sources for each change to
 the PR.
 While each of them handles a corner case which others might miss,
 would be great if we could minimize the volume of duplicated
 communication.


 Regards,
 Mridul



Re: JIRA. github and asf updates

2014-03-29 Thread Henry Saputra
With the speed of comments updates in Jira by Spark dev community +1 for
issues@ list

- Henry

On Saturday, March 29, 2014, Patrick Wendell pwend...@gmail.com wrote:

 Ah sorry I see - Jira updates are going to the dev list. Maybe that's not
 desirable. I think we should send them to the issues@ list.


 On Sat, Mar 29, 2014 at 11:16 AM, Patrick Wendell 
 pwend...@gmail.comjavascript:;
 wrote:

  Mridul,
 
  You can unsubscribe yourself from any of these sources, right?
 
  - Patrick
 
 
  On Sat, Mar 29, 2014 at 11:05 AM, Mridul Muralidharan 
  mri...@gmail.comjavascript:;
 wrote:
 
  Hi,
 
So we are now receiving updates from three sources for each change to
  the PR.
  While each of them handles a corner case which others might miss,
  would be great if we could minimize the volume of duplicated
  communication.
 
 
  Regards,
  Mridul
 
 
 



Re: JIRA. github and asf updates

2014-03-29 Thread Mridul Muralidharan
If the PR comments are going to be replicated into the jira's and they
are going to be set to dev@, then we could keep that and remove
[Github] updates ?
The last was added since discussions were happening off apache lists -
which should be handled by the jira updates ?

I dont mind the mails if they had content - this is just duplication
of the same message in three mails :-)
Btw, this is a good problem to have - a vibrant and very actively
engaged community generated a lot of meaningful traffic !
I just dont want to get distracted from it by repetitions.

Regards,
Mridul


On Sat, Mar 29, 2014 at 11:46 PM, Patrick Wendell pwend...@gmail.com wrote:
 Ah sorry I see - Jira updates are going to the dev list. Maybe that's not
 desirable. I think we should send them to the issues@ list.


 On Sat, Mar 29, 2014 at 11:16 AM, Patrick Wendell pwend...@gmail.comwrote:

 Mridul,

 You can unsubscribe yourself from any of these sources, right?

 - Patrick


 On Sat, Mar 29, 2014 at 11:05 AM, Mridul Muralidharan 
 mri...@gmail.comwrote:

 Hi,

   So we are now receiving updates from three sources for each change to
 the PR.
 While each of them handles a corner case which others might miss,
 would be great if we could minimize the volume of duplicated
 communication.


 Regards,
 Mridul





Re: JIRA. github and asf updates

2014-03-29 Thread Patrick Wendell
I'm working with infra to get the following set-up:

1. Don't post github updates to jira comments (they are too low level). If
users want these they can subscribe to commits@s.a.o.
2. Jira comment stream will go to issues@s.a.o so people can opt into that.

One thing YARN has set-up that might be cool in the future is to e-mail
*new* JIRA's to the dev list. That might be cool to set up in the future.


On Sat, Mar 29, 2014 at 1:15 PM, Mridul Muralidharan mri...@gmail.comwrote:

 If the PR comments are going to be replicated into the jira's and they
 are going to be set to dev@, then we could keep that and remove
 [Github] updates ?
 The last was added since discussions were happening off apache lists -
 which should be handled by the jira updates ?

 I dont mind the mails if they had content - this is just duplication
 of the same message in three mails :-)
 Btw, this is a good problem to have - a vibrant and very actively
 engaged community generated a lot of meaningful traffic !
 I just dont want to get distracted from it by repetitions.

 Regards,
 Mridul


 On Sat, Mar 29, 2014 at 11:46 PM, Patrick Wendell pwend...@gmail.com
 wrote:
  Ah sorry I see - Jira updates are going to the dev list. Maybe that's not
  desirable. I think we should send them to the issues@ list.
 
 
  On Sat, Mar 29, 2014 at 11:16 AM, Patrick Wendell pwend...@gmail.com
 wrote:
 
  Mridul,
 
  You can unsubscribe yourself from any of these sources, right?
 
  - Patrick
 
 
  On Sat, Mar 29, 2014 at 11:05 AM, Mridul Muralidharan mri...@gmail.com
 wrote:
 
  Hi,
 
So we are now receiving updates from three sources for each change to
  the PR.
  While each of them handles a corner case which others might miss,
  would be great if we could minimize the volume of duplicated
  communication.
 
 
  Regards,
  Mridul