You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Dennis Kieselhorst <ma...@dekies.de> on 2015/05/29 09:24:08 UTC
usage of notifications mailing list
Hi,
we have a notifications list (notifications@myfaces.apache.org) which
was used for Continuum build mails in the past. However with switch to
Jenkins build notifications are sent to commits@myfaces.apache.org. Does
anyone know why this was changed?
Cheers
Dennis
Re: usage of notifications mailing list
Posted by Dennis Kieselhorst <ma...@dekies.de>.
> So, I might be interested in knowing that builds are stable, but don't
> want to see all commits.
That's true for me and I think notifications would be even a better name
for the list. But as it's easy to filter emails I have no problem if
everything stays as it is. I suggest to remove the list from the site to
avoid further confusion.
Cheers
Dennis
Re: usage of notifications mailing list
Posted by Gerhard Petracek <gp...@apache.org>.
@mike:
yes - that was the reason (+ back then ~nobody reacted on notifications
about broken builds which were sent to the notifications-list).
regards,
gerhard
2015-05-29 13:05 GMT+02:00 Udo Schnurpfeil <ud...@schnurpfeil.de>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi,
>
> I think its reasonable to distinct:
>
> Jenkins sends only mails for failed builds and when the build is
> stable again.
>
> So, I might be interested in knowing that builds are stable, but don't
> want to see all commits.
>
> Regards,
>
> Udo
>
> Am 29.05.15 um 12:53 schrieb Mike Kienenberger:
> > I don't have any direct experience with the change, but my guess
> > would be that it didn't seem necessary to have both a commits@
> > notification list and a [builds] notifications@ list since they are
> > directly related. If you are interested in seeing code change
> > notifications, you are also interested in knowing if those code
> > changes are going to break something.
> >
> > On Fri, May 29, 2015 at 3:24 AM, Dennis Kieselhorst
> > <ma...@dekies.de> wrote:
> >> Hi,
> >>
> >> we have a notifications list (notifications@myfaces.apache.org)
> >> which was used for Continuum build mails in the past. However
> >> with switch to Jenkins build notifications are sent to
> >> commits@myfaces.apache.org. Does anyone know why this was
> >> changed?
> >>
> >> Cheers Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: GPGTools - https://gpgtools.org
>
> iQIcBAEBCgAGBQJVaEfgAAoJEAEbRra2zTKAXBQP/263m/8VSPY799FvrAYcKDsw
> SfTFLYfdubh+URiKlxPFxFIKnKNU1fhriaX5DKXzG8evAw/K5LAVur1E1g3DJpHv
> TnL7jY7t5hu6pQVEMMH5pok0bSmoyp4szD+LfSYb3WxOOQaYFUN0SHvgPoEaXFrh
> 7FB/ThNo3FjIsX9b2OWXsFIHc749O6cyK9XmFyMjTubHWaihYJQsVF9A+sgACDKv
> DcZ6Ev0lYohxA/xtdVwE7cijnupZSkawxdX/YXEEetybBcB4t9GeU//1+8JWMZuW
> qmQA3azlw8XE+Qi6eJYlYKAyNC1J2ptxy/86wnLMMP7hdcGx1PL7FrqjtTjeBvv+
> q3xRlj6tNEdp9K3tMdP8aqXzhL5u+1quO8CMBJ/Wz25PxFpB3C6VeCEv8T9GppS4
> 7XTddIkiAMv9qGuXklAFbvQwndCwIWgRbtBLgOqQ6T9BvOGuHkP4xhEBVUf0DHRN
> n5YWdNm5N10aBpraXUi2Mm8B+c5fu4U9LXQc+NOpUb/Dy4QPx5Q8cDC1DTiLp9P7
> JXI6ZhKF4YG4F/VpCNJzR05+OIJdvOz9GadMadyebZfAOYqnqwvULRtdsjJ29h6C
> B4Sz2LiOWOoZkacsoDpGuS2HQJEtqA7Oo9Mc7OLxd3O27o7o+VA91kj3LeUgpXrA
> ZucflsZCJ7jPlM9o7een
> =9cDd
> -----END PGP SIGNATURE-----
>
Re: usage of notifications mailing list
Posted by Udo Schnurpfeil <ud...@schnurpfeil.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
I think its reasonable to distinct:
Jenkins sends only mails for failed builds and when the build is
stable again.
So, I might be interested in knowing that builds are stable, but don't
want to see all commits.
Regards,
Udo
Am 29.05.15 um 12:53 schrieb Mike Kienenberger:
> I don't have any direct experience with the change, but my guess
> would be that it didn't seem necessary to have both a commits@
> notification list and a [builds] notifications@ list since they are
> directly related. If you are interested in seeing code change
> notifications, you are also interested in knowing if those code
> changes are going to break something.
>
> On Fri, May 29, 2015 at 3:24 AM, Dennis Kieselhorst
> <ma...@dekies.de> wrote:
>> Hi,
>>
>> we have a notifications list (notifications@myfaces.apache.org)
>> which was used for Continuum build mails in the past. However
>> with switch to Jenkins build notifications are sent to
>> commits@myfaces.apache.org. Does anyone know why this was
>> changed?
>>
>> Cheers Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJVaEfgAAoJEAEbRra2zTKAXBQP/263m/8VSPY799FvrAYcKDsw
SfTFLYfdubh+URiKlxPFxFIKnKNU1fhriaX5DKXzG8evAw/K5LAVur1E1g3DJpHv
TnL7jY7t5hu6pQVEMMH5pok0bSmoyp4szD+LfSYb3WxOOQaYFUN0SHvgPoEaXFrh
7FB/ThNo3FjIsX9b2OWXsFIHc749O6cyK9XmFyMjTubHWaihYJQsVF9A+sgACDKv
DcZ6Ev0lYohxA/xtdVwE7cijnupZSkawxdX/YXEEetybBcB4t9GeU//1+8JWMZuW
qmQA3azlw8XE+Qi6eJYlYKAyNC1J2ptxy/86wnLMMP7hdcGx1PL7FrqjtTjeBvv+
q3xRlj6tNEdp9K3tMdP8aqXzhL5u+1quO8CMBJ/Wz25PxFpB3C6VeCEv8T9GppS4
7XTddIkiAMv9qGuXklAFbvQwndCwIWgRbtBLgOqQ6T9BvOGuHkP4xhEBVUf0DHRN
n5YWdNm5N10aBpraXUi2Mm8B+c5fu4U9LXQc+NOpUb/Dy4QPx5Q8cDC1DTiLp9P7
JXI6ZhKF4YG4F/VpCNJzR05+OIJdvOz9GadMadyebZfAOYqnqwvULRtdsjJ29h6C
B4Sz2LiOWOoZkacsoDpGuS2HQJEtqA7Oo9Mc7OLxd3O27o7o+VA91kj3LeUgpXrA
ZucflsZCJ7jPlM9o7een
=9cDd
-----END PGP SIGNATURE-----
Re: usage of notifications mailing list
Posted by Mike Kienenberger <mk...@gmail.com>.
I don't have any direct experience with the change, but my guess would
be that it didn't seem necessary to have both a commits@ notification
list and a [builds] notifications@ list since they are directly
related. If you are interested in seeing code change notifications,
you are also interested in knowing if those code changes are going to
break something.
On Fri, May 29, 2015 at 3:24 AM, Dennis Kieselhorst <ma...@dekies.de> wrote:
> Hi,
>
> we have a notifications list (notifications@myfaces.apache.org) which
> was used for Continuum build mails in the past. However with switch to
> Jenkins build notifications are sent to commits@myfaces.apache.org. Does
> anyone know why this was changed?
>
> Cheers
> Dennis