You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by Thomas Weise <th...@datatorrent.com> on 2016/04/21 21:45:19 UTC
JIRA traffic on the dev list
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
Re: JIRA traffic on the dev list
Posted by Sandesh Hegde <sa...@datatorrent.com>.
+1
On Thu, Apr 21, 2016 at 12:45 PM Thomas Weise <th...@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
>
Re: JIRA traffic on the dev list
Posted by Thomas Weise <th...@datatorrent.com>.
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
<de...@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....@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 <am...@datatorrent.com> wrote:
>>>
>>> +1
>>>>
>>>> Thks
>>>> Amol
>>>>
>>>> On Thu, Apr 21, 2016 at 1:16 PM, Siyuan Hua <si...@datatorrent.com>
>>>> wrote:
>>>>
>>>> +1
>>>>>
>>>>> On Thu, Apr 21, 2016 at 12:56 PM, David Yan <da...@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
>>>>>>>
>>>>>>>
>>
Re: JIRA traffic on the dev list
Posted by Yogi Devendra <de...@gmail.com>.
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....@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 <am...@datatorrent.com> wrote:
>>
>> +1
>>>
>>> Thks
>>> Amol
>>>
>>> On Thu, Apr 21, 2016 at 1:16 PM, Siyuan Hua <si...@datatorrent.com>
>>> wrote:
>>>
>>> +1
>>>>
>>>> On Thu, Apr 21, 2016 at 12:56 PM, David Yan <da...@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
>>>>>>
>>>>>>
>
Re: JIRA traffic on the dev list
Posted by Vlad Rozov <v....@datatorrent.com>.
+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 <am...@datatorrent.com> wrote:
>
>> +1
>>
>> Thks
>> Amol
>>
>> On Thu, Apr 21, 2016 at 1:16 PM, Siyuan Hua <si...@datatorrent.com>
>> wrote:
>>
>>> +1
>>>
>>> On Thu, Apr 21, 2016 at 12:56 PM, David Yan <da...@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
>>>>>
Re: JIRA traffic on the dev list
Posted by Devendra Tagare <de...@datatorrent.com>.
+1
Thanks,
Dev
On Thu, Apr 21, 2016 at 2:01 PM, Amol Kekre <am...@datatorrent.com> wrote:
> +1
>
> Thks
> Amol
>
> On Thu, Apr 21, 2016 at 1:16 PM, Siyuan Hua <si...@datatorrent.com>
> wrote:
>
> > +1
> >
> > On Thu, Apr 21, 2016 at 12:56 PM, David Yan <da...@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
> > > >
> > >
> >
>
Re: JIRA traffic on the dev list
Posted by Amol Kekre <am...@datatorrent.com>.
+1
Thks
Amol
On Thu, Apr 21, 2016 at 1:16 PM, Siyuan Hua <si...@datatorrent.com> wrote:
> +1
>
> On Thu, Apr 21, 2016 at 12:56 PM, David Yan <da...@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 <th...@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
> > >
> >
>
Re: JIRA traffic on the dev list
Posted by Siyuan Hua <si...@datatorrent.com>.
+1
On Thu, Apr 21, 2016 at 12:56 PM, David Yan <da...@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 <th...@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
> >
>
Re: JIRA traffic on the dev list
Posted by David Yan <da...@datatorrent.com>.
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 <th...@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
>