phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva" <tdsi...@salesforce.com>
Subject Re: [DISCUSS] reduce notifications to phoenix-dev list
Date Wed, 01 Aug 2018 17:59:28 GMT
Sure I will file an INFRA ticket to change the behavior to send an email to
the issues list when an issue is commented on or issue comment is edited or
deleted.
Should we also redirect the ASF GitHub Bot emails to the issues list
instead of the dev list?




On Wed, Aug 1, 2018 at 10:20 AM, Josh Elser <josh.elser@gmail.com> wrote:

> Thomas -- we should be good on the mailing list being available.
>
> Can we flip Jira over to use this new list?
>
> On 2018/07/30 16:22:07, Josh Elser <josh.elser@gmail.com> wrote: > Done.
> I can't seem to find a way to figure out who the moderators of the >
> currents lists are, so I put down myself, James (sorry ^.^), and Thomas ;)
>
>
>> On 2018/07/26 17:39:49, "Thomas D'Silva" <tdsilva@salesforce.com>
>> wrote:  > Josh,
>> > > Only apache members or pmc chairs can create a new mailing list (
>> > https://selfserve.apache.org/mail.html).
>> > Can you create issues@phoenix.apache.org?
>> > > Thanks,
>> > Thomas
>> > > On Wed, Jul 25, 2018 at 9:20 AM, Josh Elser <josh.elser@gmail.com>
>> wrote:
>> > > > I think this would be a nice thing to do.
>> > >
>> > >
>> > > On 7/24/18 8:17 PM, Thomas D'Silva wrote:
>> > >
>> > >> Do folks think we need an issues mailing list similar to HBase that
>> will
>> > >> receive notifications about comments?
>> > >>
>> > >> On Tue, Jul 24, 2018 at 5:10 PM, Thomas D'Silva <
>> tdsilva@salesforce.com>
>> > >> wrote:
>> > >>
>> > >> Thanks Josh, I filed an INFRA Jira and updated the notification
>> scheme.
>> > >>> dev@phoenix.apache.org will no longer receive notifications when
an
>> > >>> issue
>> > >>> is commented on or a comment is edited/deleted.
>> > >>>
>> > >>> On Thu, Jul 12, 2018 at 1:41 PM, Josh Elser <josh.elser@gmail.com>
>> > >>> wrote:
>> > >>>
>> > >>> I think INFRA keeps these locked down. Just requires an INFRA JIRA
>> issue,
>> > >>>> I'd guess asking them to change it.
>> > >>>>
>> > >>>>
>> > >>>> On 7/12/18 1:53 PM, Thomas D'Silva wrote:
>> > >>>>
>> > >>>> Josh,
>> > >>>>>
>> > >>>>> Do you know how to edit the notification scheme here
>> > >>>>> https://issues.apache.org/jira/plugins/servlet/project-confi
>> > >>>>> g/PHOENIX/notifications
>> > >>>>> ?
>> > >>>>> I don't see an edit button.
>> > >>>>>
>> > >>>>> Thanks,
>> > >>>>> Thomas
>> > >>>>>
>> > >>>>> On Thu, Jul 12, 2018 at 7:09 AM, James Taylor <
>> jamestaylor@apache.org>
>> > >>>>> wrote:
>> > >>>>>
>> > >>>>> +1
>> > >>>>>
>> > >>>>>>
>> > >>>>>> On Thu, Jul 12, 2018 at 5:51 AM Josh Elser <josh.elser@gmail.com
>> >
>> > >>>>>> wrote:
>> > >>>>>>
>> > >>>>>> Fine by me.
>> > >>>>>>
>> > >>>>>>>
>> > >>>>>>> On 7/11/18 9:50 PM, Thomas D'Silva wrote:
>> > >>>>>>>
>> > >>>>>>> I think we should reduce the number of notifications
that are
>> sent to
>> > >>>>>>>>
>> > >>>>>>>> the
>> > >>>>>>>
>> > >>>>>>
>> > >>>>>> phoenix-dev list.
>> > >>>>>>>
>> > >>>>>>>> The notification scheme we use is located here
:
>> > >>>>>>>>
>> > >>>>>>>> https://issues.apache.org/
>> > >>>>>>>
>> > >>>>>>> jira/plugins/servlet/project-config/PHOENIX/notifications
>> > >>>>>>>>
>> > >>>>>>>> Maybe we don't need to notify the dev list
when an issue is
>> updated,
>> > >>>>>>>>
>> > >>>>>>>> or a
>> > >>>>>>>
>> > >>>>>>
>> > >>>>>> comment is created/edited/deleted. People watching
a particular
>> issue
>> > >>>>>>>
>> > >>>>>>>>
>> > >>>>>>>> would
>> > >>>>>>>
>> > >>>>>>> still see all the changes.
>> > >>>>>>>> This would be similar to how other projects
like HBase and
>> Calcite
>> > >>>>>>>>
>> > >>>>>>>> operate.
>> > >>>>>>>
>> > >>>>>>>
>> > >>>>>>>> Thanks,
>> > >>>>>>>> Thomas
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>>
>> > >>>>>>
>> > >>>>>
>> > >>>
>> > >>
>> >
>>
>

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