You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Bikas Saha <bi...@apache.org> on 2015/11/10 10:35:51 UTC
Sending JIRA creations to dev list
Folks,
Tez sends new jira creations and jira resolution emails to the issues list.
It would be good if new jira creations and jira resolutions are also sent to
the dev list. This enables subscribers to track new issues/bugs without
being inundated in the high traffic issues list (which has emails for every
jira update). Hadoop also sends jira creation/resolution emails to the dev
list.
If there are no objections, I will create an INFRA ticket to add the dev
list for jira creation/resolution emails (in addition to the existing issues
list).
Thanks
Bikas
Re: Sending JIRA creations to dev list
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
Sounds a good idea to me.
Thanks,
- Tsuyoshi
On Wed, Nov 11, 2015 at 1:52 PM, Bikas Saha <bi...@apache.org> wrote:
> Right.
>
> -----Original Message-----
> From: Siddharth Seth [mailto:sseth@apache.org]
> Sent: Tuesday, November 10, 2015 10:16 AM
> To: dev@tez.apache.org
> Subject: Re: Sending JIRA creations to dev list
>
> Sounds good. Clarifying - jira creation messages will go to both dev and issues, Subsequent updates will go to issues ?
>
> On Tue, Nov 10, 2015 at 10:05 AM, Hitesh Shah <hi...@apache.org> wrote:
>
>> Sounds like a good idea. +1.
>>
>> — Hitesh
>>
>>
>> On Nov 10, 2015, at 1:35 AM, Bikas Saha <bi...@apache.org> wrote:
>>
>> > Folks,
>> >
>> >
>> >
>> > Tez sends new jira creations and jira resolution emails to the
>> > issues
>> list.
>> > It would be good if new jira creations and jira resolutions are also
>> sent to
>> > the dev list. This enables subscribers to track new issues/bugs
>> > without being inundated in the high traffic issues list (which has
>> > emails for
>> every
>> > jira update). Hadoop also sends jira creation/resolution emails to
>> > the
>> dev
>> > list.
>> >
>> >
>> >
>> > If there are no objections, I will create an INFRA ticket to add the
>> > dev list for jira creation/resolution emails (in addition to the
>> > existing
>> issues
>> > list).
>> >
>> >
>> >
>> > Thanks
>> >
>> > Bikas
>> >
>> >
>> >
>>
>>
RE: Sending JIRA creations to dev list
Posted by Bikas Saha <bi...@apache.org>.
Right.
-----Original Message-----
From: Siddharth Seth [mailto:sseth@apache.org]
Sent: Tuesday, November 10, 2015 10:16 AM
To: dev@tez.apache.org
Subject: Re: Sending JIRA creations to dev list
Sounds good. Clarifying - jira creation messages will go to both dev and issues, Subsequent updates will go to issues ?
On Tue, Nov 10, 2015 at 10:05 AM, Hitesh Shah <hi...@apache.org> wrote:
> Sounds like a good idea. +1.
>
> — Hitesh
>
>
> On Nov 10, 2015, at 1:35 AM, Bikas Saha <bi...@apache.org> wrote:
>
> > Folks,
> >
> >
> >
> > Tez sends new jira creations and jira resolution emails to the
> > issues
> list.
> > It would be good if new jira creations and jira resolutions are also
> sent to
> > the dev list. This enables subscribers to track new issues/bugs
> > without being inundated in the high traffic issues list (which has
> > emails for
> every
> > jira update). Hadoop also sends jira creation/resolution emails to
> > the
> dev
> > list.
> >
> >
> >
> > If there are no objections, I will create an INFRA ticket to add the
> > dev list for jira creation/resolution emails (in addition to the
> > existing
> issues
> > list).
> >
> >
> >
> > Thanks
> >
> > Bikas
> >
> >
> >
>
>
Re: Sending JIRA creations to dev list
Posted by Siddharth Seth <ss...@apache.org>.
Sounds good. Clarifying - jira creation messages will go to both dev and
issues, Subsequent updates will go to issues ?
On Tue, Nov 10, 2015 at 10:05 AM, Hitesh Shah <hi...@apache.org> wrote:
> Sounds like a good idea. +1.
>
> — Hitesh
>
>
> On Nov 10, 2015, at 1:35 AM, Bikas Saha <bi...@apache.org> wrote:
>
> > Folks,
> >
> >
> >
> > Tez sends new jira creations and jira resolution emails to the issues
> list.
> > It would be good if new jira creations and jira resolutions are also
> sent to
> > the dev list. This enables subscribers to track new issues/bugs without
> > being inundated in the high traffic issues list (which has emails for
> every
> > jira update). Hadoop also sends jira creation/resolution emails to the
> dev
> > list.
> >
> >
> >
> > If there are no objections, I will create an INFRA ticket to add the dev
> > list for jira creation/resolution emails (in addition to the existing
> issues
> > list).
> >
> >
> >
> > Thanks
> >
> > Bikas
> >
> >
> >
>
>
Re: Sending JIRA creations to dev list
Posted by Hitesh Shah <hi...@apache.org>.
Sounds like a good idea. +1.
— Hitesh
On Nov 10, 2015, at 1:35 AM, Bikas Saha <bi...@apache.org> wrote:
> Folks,
>
>
>
> Tez sends new jira creations and jira resolution emails to the issues list.
> It would be good if new jira creations and jira resolutions are also sent to
> the dev list. This enables subscribers to track new issues/bugs without
> being inundated in the high traffic issues list (which has emails for every
> jira update). Hadoop also sends jira creation/resolution emails to the dev
> list.
>
>
>
> If there are no objections, I will create an INFRA ticket to add the dev
> list for jira creation/resolution emails (in addition to the existing issues
> list).
>
>
>
> Thanks
>
> Bikas
>
>
>
Re: Sending JIRA creations to dev list
Posted by "Jianfeng (Jeff) Zhang" <jz...@hortonworks.com>.
+1
Best Regard,
Jeff Zhang
On 11/10/15, 5:35 PM, "Bikas Saha" <bi...@apache.org> wrote:
>Folks,
>
>
>
>Tez sends new jira creations and jira resolution emails to the issues
>list.
>It would be good if new jira creations and jira resolutions are also sent
>to
>the dev list. This enables subscribers to track new issues/bugs without
>being inundated in the high traffic issues list (which has emails for
>every
>jira update). Hadoop also sends jira creation/resolution emails to the dev
>list.
>
>
>
>If there are no objections, I will create an INFRA ticket to add the dev
>list for jira creation/resolution emails (in addition to the existing
>issues
>list).
>
>
>
>Thanks
>
>Bikas
>
>
>