You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2013/03/17 20:09:54 UTC
[DISCUSS] Separating jira and jenkins emails from dev@ list
I have been searching for an old email in our mailing list and I have
just realized that the archives are literally polluted with something
like " Build failed in Jenkins" or " [jira] [Commented] "
In every given month there are screens and screens of the emails that
either dups of the information available elsewhere - i.e. Jira, or
useless in the retrospect - Jenkins build failure notifications are of
no importance in a couple of days usually.
What do you guys think about redirecting all that traffic to a
separate list and leave the dev@ for human beings? Say, we might have
another list ci@ or similar where all jira comments and jenkins
notifications will be sent.
I don't buy the argument like "this will hide important notifications
from the developers" simply because most of us are filtering these
notifications one way or another in order to make inbox inflow
manageable. For instance, I have a filter that moves all JIRA and CI
notifications for different projects to their appropriate mailboxes
that are being checked upon when I have time for it, etc.
So, what do you think?
Cos
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Wing Yew Poon <wy...@cloudera.com>.
+1
On Tue, Mar 19, 2013 at 1:22 AM, Bruno Mahé <bm...@apache.org> wrote:
> On 03/17/2013 12:09 PM, Konstantin Boudnik wrote:
>>
>> I have been searching for an old email in our mailing list and I have
>> just realized that the archives are literally polluted with something
>> like " Build failed in Jenkins" or " [jira] [Commented] "
>>
>> In every given month there are screens and screens of the emails that
>> either dups of the information available elsewhere - i.e. Jira, or
>> useless in the retrospect - Jenkins build failure notifications are of
>> no importance in a couple of days usually.
>>
>> What do you guys think about redirecting all that traffic to a
>> separate list and leave the dev@ for human beings? Say, we might have
>> another list ci@ or similar where all jira comments and jenkins
>> notifications will be sent.
>>
>> I don't buy the argument like "this will hide important notifications
>> from the developers" simply because most of us are filtering these
>> notifications one way or another in order to make inbox inflow
>> manageable. For instance, I have a filter that moves all JIRA and CI
>> notifications for different projects to their appropriate mailboxes
>> that are being checked upon when I have time for it, etc.
>>
>> So, what do you think?
>> Cos
>>
>
> +1
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Bruno Mahé <bm...@apache.org>.
On 03/17/2013 12:09 PM, Konstantin Boudnik wrote:
> I have been searching for an old email in our mailing list and I have
> just realized that the archives are literally polluted with something
> like " Build failed in Jenkins" or " [jira] [Commented] "
>
> In every given month there are screens and screens of the emails that
> either dups of the information available elsewhere - i.e. Jira, or
> useless in the retrospect - Jenkins build failure notifications are of
> no importance in a couple of days usually.
>
> What do you guys think about redirecting all that traffic to a
> separate list and leave the dev@ for human beings? Say, we might have
> another list ci@ or similar where all jira comments and jenkins
> notifications will be sent.
>
> I don't buy the argument like "this will hide important notifications
> from the developers" simply because most of us are filtering these
> notifications one way or another in order to make inbox inflow
> manageable. For instance, I have a filter that moves all JIRA and CI
> notifications for different projects to their appropriate mailboxes
> that are being checked upon when I have time for it, etc.
>
> So, what do you think?
> Cos
>
+1
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Paulo Ricardo Paz Vital <pv...@linux.vnet.ibm.com>.
+1, even not sure if I can vote!! :-D
I agree with Cos and Arun arguments. I have personal filters to move
that kind of emails to a different folders, but two different mailling
lists sounds good when we try a search in the mail archives - I did a
search last week in the archives and got some "bad" results.
Regards, Paulo.
On 03/18/2013 01:25 PM, Arun Singla wrote:
> +1, and if someone wants to see all those (jenkins/jira) emails they can
> subscribe to ci@
>
> ArunSingla
>
> On Mon, Mar 18, 2013 at 9:18 AM, Roman Shaposhnik <rv...@apache.org> wrote:
>
>> On Sun, Mar 17, 2013 at 12:09 PM, Konstantin Boudnik <co...@apache.org>
>> wrote:
>>> I have been searching for an old email in our mailing list and I have
>>> just realized that the archives are literally polluted with something
>>> like " Build failed in Jenkins" or " [jira] [Commented] "
>>>
>>> In every given month there are screens and screens of the emails that
>>> either dups of the information available elsewhere - i.e. Jira, or
>>> useless in the retrospect - Jenkins build failure notifications are of
>>> no importance in a couple of days usually.
>>>
>>> What do you guys think about redirecting all that traffic to a
>>> separate list and leave the dev@ for human beings? Say, we might have
>>> another list ci@ or similar where all jira comments and jenkins
>>> notifications will be sent.
>>>
>>> I don't buy the argument like "this will hide important notifications
>>> from the developers" simply because most of us are filtering these
>>> notifications one way or another in order to make inbox inflow
>>> manageable. For instance, I have a filter that moves all JIRA and CI
>>> notifications for different projects to their appropriate mailboxes
>>> that are being checked upon when I have time for it, etc.
>>>
>>> So, what do you think?
>>
>> +1. I think we've grown quite a bit for this to make sense.
>>
>> Thanks,
>> Roman.
>>
>
--
Paulo Ricardo Paz Vital, Staff Software Engineer
Linux Technology Center, IBM Systems & Technology Group
-------------------------------------------------------
IBM
Rodovia SP101, km9 - ZIP: 13186-900
Hortolândia, SP - Brazil
Phone: +55-19-2132-2336
e-mail: pvital@linux.vnet.ibm.com
http://www.ibm.com/linux/ltc
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Arun Singla <ar...@cloudera.com>.
+1, and if someone wants to see all those (jenkins/jira) emails they can
subscribe to ci@
ArunSingla
On Mon, Mar 18, 2013 at 9:18 AM, Roman Shaposhnik <rv...@apache.org> wrote:
> On Sun, Mar 17, 2013 at 12:09 PM, Konstantin Boudnik <co...@apache.org>
> wrote:
> > I have been searching for an old email in our mailing list and I have
> > just realized that the archives are literally polluted with something
> > like " Build failed in Jenkins" or " [jira] [Commented] "
> >
> > In every given month there are screens and screens of the emails that
> > either dups of the information available elsewhere - i.e. Jira, or
> > useless in the retrospect - Jenkins build failure notifications are of
> > no importance in a couple of days usually.
> >
> > What do you guys think about redirecting all that traffic to a
> > separate list and leave the dev@ for human beings? Say, we might have
> > another list ci@ or similar where all jira comments and jenkins
> > notifications will be sent.
> >
> > I don't buy the argument like "this will hide important notifications
> > from the developers" simply because most of us are filtering these
> > notifications one way or another in order to make inbox inflow
> > manageable. For instance, I have a filter that moves all JIRA and CI
> > notifications for different projects to their appropriate mailboxes
> > that are being checked upon when I have time for it, etc.
> >
> > So, what do you think?
>
> +1. I think we've grown quite a bit for this to make sense.
>
> Thanks,
> Roman.
>
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Anatoli Fomenko <af...@yahoo.com>.
+1
Anatoli
________________________________
From: Konstantin Boudnik <co...@apache.org>
To: dev@bigtop.apache.org
Sent: Sunday, March 24, 2013 1:39 PM
Subject: Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Looks like everybody is in favor. I am going to file INFRA ticket and once the
maillist is created, we'll deal with the builds' and JIRA's notifications.
Cos
On Mon, Mar 18, 2013 at 09:18AM, Roman Shaposhnik wrote:
> On Sun, Mar 17, 2013 at 12:09 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > I have been searching for an old email in our mailing list and I have
> > just realized that the archives are literally polluted with something
> > like " Build failed in Jenkins" or " [jira] [Commented] "
> >
> > In every given month there are screens and screens of the emails that
> > either dups of the information available elsewhere - i.e. Jira, or
> > useless in the retrospect - Jenkins build failure notifications are of
> > no importance in a couple of days usually.
> >
> > What do you guys think about redirecting all that traffic to a
> > separate list and leave the dev@ for human beings? Say, we might have
> > another list ci@ or similar where all jira comments and jenkins
> > notifications will be sent.
> >
> > I don't buy the argument like "this will hide important notifications
> > from the developers" simply because most of us are filtering these
> > notifications one way or another in order to make inbox inflow
> > manageable. For instance, I have a filter that moves all JIRA and CI
> > notifications for different projects to their appropriate mailboxes
> > that are being checked upon when I have time for it, etc.
> >
> > So, what do you think?
>
> +1. I think we've grown quite a bit for this to make sense.
>
> Thanks,
> Roman.
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Roman Shaposhnik <rv...@apache.org>.
On Sun, Mar 24, 2013 at 1:39 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Looks like everybody is in favor. I am going to file INFRA ticket and once the
> maillist is created, we'll deal with the builds' and JIRA's notifications.
Thanks a million, Cos!
Thanks,
Roman
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Konstantin Boudnik <co...@apache.org>.
Looks like everybody is in favor. I am going to file INFRA ticket and once the
maillist is created, we'll deal with the builds' and JIRA's notifications.
Cos
On Mon, Mar 18, 2013 at 09:18AM, Roman Shaposhnik wrote:
> On Sun, Mar 17, 2013 at 12:09 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > I have been searching for an old email in our mailing list and I have
> > just realized that the archives are literally polluted with something
> > like " Build failed in Jenkins" or " [jira] [Commented] "
> >
> > In every given month there are screens and screens of the emails that
> > either dups of the information available elsewhere - i.e. Jira, or
> > useless in the retrospect - Jenkins build failure notifications are of
> > no importance in a couple of days usually.
> >
> > What do you guys think about redirecting all that traffic to a
> > separate list and leave the dev@ for human beings? Say, we might have
> > another list ci@ or similar where all jira comments and jenkins
> > notifications will be sent.
> >
> > I don't buy the argument like "this will hide important notifications
> > from the developers" simply because most of us are filtering these
> > notifications one way or another in order to make inbox inflow
> > manageable. For instance, I have a filter that moves all JIRA and CI
> > notifications for different projects to their appropriate mailboxes
> > that are being checked upon when I have time for it, etc.
> >
> > So, what do you think?
>
> +1. I think we've grown quite a bit for this to make sense.
>
> Thanks,
> Roman.
Re: [DISCUSS] Separating jira and jenkins emails from dev@ list
Posted by Roman Shaposhnik <rv...@apache.org>.
On Sun, Mar 17, 2013 at 12:09 PM, Konstantin Boudnik <co...@apache.org> wrote:
> I have been searching for an old email in our mailing list and I have
> just realized that the archives are literally polluted with something
> like " Build failed in Jenkins" or " [jira] [Commented] "
>
> In every given month there are screens and screens of the emails that
> either dups of the information available elsewhere - i.e. Jira, or
> useless in the retrospect - Jenkins build failure notifications are of
> no importance in a couple of days usually.
>
> What do you guys think about redirecting all that traffic to a
> separate list and leave the dev@ for human beings? Say, we might have
> another list ci@ or similar where all jira comments and jenkins
> notifications will be sent.
>
> I don't buy the argument like "this will hide important notifications
> from the developers" simply because most of us are filtering these
> notifications one way or another in order to make inbox inflow
> manageable. For instance, I have a filter that moves all JIRA and CI
> notifications for different projects to their appropriate mailboxes
> that are being checked upon when I have time for it, etc.
>
> So, what do you think?
+1. I think we've grown quite a bit for this to make sense.
Thanks,
Roman.