apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Weise <tho...@datatorrent.com>
Subject Re: JIRA traffic on the dev list
Date Fri, 22 Apr 2016 04:42:32 GMT
We have a commits list. But I don't think PR discussions belong on that list.

Thomas

On Thu, Apr 21, 2016 at 9:39 PM, Yogi Devendra
<devendra.vyavahare@gmail.com> wrote:
> echo $David.
> +1
>
> @Vlad
>
> Why do we need commits mailing list separate from issues mailing list?
>
> ~ Yogi
>
> On 22 April 2016 at 03:06, Vlad Rozov <v.rozov@datatorrent.com> wrote:
>
>> +1. I think we should also consider creating commits mailing list and
>> routing PR discussion to it.
>>
>>
>> Thank you,
>>
>> Vlad
>>
>>
>>
>> On 4/21/16 14:09, Devendra Tagare wrote:
>>
>>> +1
>>>
>>> Thanks,
>>> Dev
>>>
>>> On Thu, Apr 21, 2016 at 2:01 PM, Amol Kekre <amol@datatorrent.com> wrote:
>>>
>>> +1
>>>>
>>>> Thks
>>>> Amol
>>>>
>>>> On Thu, Apr 21, 2016 at 1:16 PM, Siyuan Hua <siyuan@datatorrent.com>
>>>> wrote:
>>>>
>>>> +1
>>>>>
>>>>> On Thu, Apr 21, 2016 at 12:56 PM, David Yan <david@datatorrent.com>
>>>>>
>>>> wrote:
>>>>
>>>>> I strongly agree with this statement in the email, "high-volume lists
>>>>>> discourage part-time contributors".
>>>>>>
>>>>>> If I understand the email correctly:
>>>>>>
>>>>>> issues@ receives ALL JIRA notifications
>>>>>> dev@ receives only JIRA ticket *creation* notification
>>>>>>
>>>>>> I'm +1 for adopting this policy for Apex.
>>>>>>
>>>>>> David
>>>>>>
>>>>>> On Thu, Apr 21, 2016 at 12:45 PM, Thomas Weise <thomas@datatorrent.com
>>>>>> wrote:
>>>>>>
>>>>>> We discussed it a while ago.
>>>>>>>
>>>>>>> This could be a compromise:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>> http://mail-archives.apache.org/mod_mbox/calcite-dev/201603.mbox/%3C252845BC-7868-4B83-8B20-6C86ED22B795@apache.org%3E
>>>>
>>>>> Thomas
>>>>>>>
>>>>>>>
>>

Mime
View raw message