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
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 th
With the speed of comments updates in Jira by Spark dev community +1 for
issues@ list
- Henry
On Saturday, March 29, 2014, Patrick Wendell 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 Sa
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 wrote:
> Mridul,
>
> You can unsubscribe yourself from any of these sources, right?
>
> - Patrick
>
>
> On Sat,
Mridul,
You can unsubscribe yourself from any of these sources, right?
- Patrick
On Sat, Mar 29, 2014 at 11:05 AM, Mridul Muralidharan 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 migh
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
