All-

I'm wondering if it might make more sense to send the Jenkins build
notifications to the notifications list, rather than the dev list.

I see two advantages:

1) The dev list is more "pure" in terms of humans-only, which can make
it easier for developers to interact without feeling spammed.
2) Those who don't want to see any automated notifications can filter
them out more easily.

And one disadvantage:

1) Developers signed up to the dev list may not want to sign up for a
second list to get notifications about build failures they caused with
their commits.

The disadvantage can be mitigated, I think, if Jenkins is smart enough
to know who caused the commit that failed, and can be configured to
send a notice back to that person directly, in addition to the
notifications list.

(Also, on a related note, I've attached the importable GMail filters
that I use which you may find useful to organize your GMail. Feel free
to use.)

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii

On Sun, Oct 14, 2012 at 9:09 AM, Christopher Tubbs <[EMAIL PROTECTED]> wrote:
> All-
>
> I'm wondering if it might make more sense to send the Jenkins build
> notifications to the notifications list, rather than the dev list.

+1

>
> I see two advantages:
>
> 1) The dev list is more "pure" in terms of humans-only, which can make
> it easier for developers to interact without feeling spammed.
> 2) Those who don't want to see any automated notifications can filter
> them out more easily.
>
> And one disadvantage:
>
> 1) Developers signed up to the dev list may not want to sign up for a
> second list to get notifications about build failures they caused with
> their commits.
>
> The disadvantage can be mitigated, I think, if Jenkins is smart enough
> to know who caused the commit that failed, and can be configured to
> send a notice back to that person directly, in addition to the
> notifications list.
>
> (Also, on a related note, I've attached the importable GMail filters
> that I use which you may find useful to organize your GMail. Feel free
> to use.)
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii

+1 and thanks for the filters

On Sun, Oct 14, 2012 at 9:09 AM, Christopher Tubbs <[EMAIL PROTECTED]>wrote:

> All-
>
> I'm wondering if it might make more sense to send the Jenkins build
> notifications to the notifications list, rather than the dev list.
>
> I see two advantages:
>
> 1) The dev list is more "pure" in terms of humans-only, which can make
> it easier for developers to interact without feeling spammed.
> 2) Those who don't want to see any automated notifications can filter
> them out more easily.
>
> And one disadvantage:
>
> 1) Developers signed up to the dev list may not want to sign up for a
> second list to get notifications about build failures they caused with
> their commits.
>
> The disadvantage can be mitigated, I think, if Jenkins is smart enough
> to know who caused the commit that failed, and can be configured to
> send a notice back to that person directly, in addition to the
> notifications list.
>
> (Also, on a related note, I've attached the importable GMail filters
> that I use which you may find useful to organize your GMail. Feel free
> to use.)
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>

--
~John

Pending objections, I'll make this change later today.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Mon, Oct 15, 2012 at 1:55 PM, John Vines <[EMAIL PROTECTED]> wrote:
> +1 and thanks for the filters
>
> On Sun, Oct 14, 2012 at 9:09 AM, Christopher Tubbs <[EMAIL PROTECTED]>wrote:
>
>> All-
>>
>> I'm wondering if it might make more sense to send the Jenkins build
>> notifications to the notifications list, rather than the dev list.
>>
>> I see two advantages:
>>
>> 1) The dev list is more "pure" in terms of humans-only, which can make
>> it easier for developers to interact without feeling spammed.
>> 2) Those who don't want to see any automated notifications can filter
>> them out more easily.
>>
>> And one disadvantage:
>>
>> 1) Developers signed up to the dev list may not want to sign up for a
>> second list to get notifications about build failures they caused with
>> their commits.
>>
>> The disadvantage can be mitigated, I think, if Jenkins is smart enough
>> to know who caused the commit that failed, and can be configured to
>> send a notice back to that person directly, in addition to the
>> notifications list.
>>
>> (Also, on a related note, I've attached the importable GMail filters
>> that I use which you may find useful to organize your GMail. Feel free
>> to use.)
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>
>
>
> --
> ~John

For those interested, I've attached a slightly better set of GMail
filters that I use, that you are free to import and use. These will
also separate the Jenkins notifications from the JIRA notifications,
and will also separate tickets that are mailed directly to you from
JIRA, as a result of you "watching" a ticket, from all the other
ticket updates that are sent to the notifications list. There's also
some other, general Apache lists which, if you're subscribed to those,
you may find useful.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, Oct 16, 2012 at 1:46 PM, Christopher Tubbs <[EMAIL PROTECTED]> wrote:
> Pending objections, I'll make this change later today.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Mon, Oct 15, 2012 at 1:55 PM, John Vines <[EMAIL PROTECTED]> wrote:
>> +1 and thanks for the filters
>>
>> On Sun, Oct 14, 2012 at 9:09 AM, Christopher Tubbs <[EMAIL PROTECTED]>wrote:
>>
>>> All-
>>>
>>> I'm wondering if it might make more sense to send the Jenkins build
>>> notifications to the notifications list, rather than the dev list.
>>>
>>> I see two advantages:
>>>
>>> 1) The dev list is more "pure" in terms of humans-only, which can make
>>> it easier for developers to interact without feeling spammed.
>>> 2) Those who don't want to see any automated notifications can filter
>>> them out more easily.
>>>
>>> And one disadvantage:
>>>
>>> 1) Developers signed up to the dev list may not want to sign up for a
>>> second list to get notifications about build failures they caused with
>>> their commits.
>>>
>>> The disadvantage can be mitigated, I think, if Jenkins is smart enough
>>> to know who caused the commit that failed, and can be configured to
>>> send a notice back to that person directly, in addition to the
>>> notifications list.
>>>
>>> (Also, on a related note, I've attached the importable GMail filters
>>> that I use which you may find useful to organize your GMail. Feel free
>>> to use.)
>>>
>>> --
>>> Christopher L Tubbs II
>>> http://gravatar.com/ctubbsii
>>>
>>
>>
>>
>> --
>> ~John