dev list.
>>>
>>> So def a +1 for changing the settings.
>>>
>>> Patrick
>>>
>>>> Am 01.09.2020 um 15:59 schrieb Dominik Riemer :
>>>>
>>>> Hi all,
>>>>
>>>> currently, Jira notific
o the iss...@streampipes.apache.org
> >> <mailto:iss...@streampipes.apache.org> list.
> >>
> >>
> >>
> >> My feeling is that the increasing number of Jira notifications on this list
> >> "pollutes" the dev list
sue
>>> would be an option?
>>>
>>> Theoretically it should halve the load and the close-emails don't really
>>> bring much benefit ;-)
>>>
>>> Chris
>>>
>>> Am 01.09.20, 16:26 schrieb "Dominik
ssues, I have no
>> objections.
>> Perhaps just sending an email on creation, but not on closing an issue would
>> be an option?
>>
>> Theoretically it should halve the load and the close-emails don't really
>> bring much benefit ;-)
>>
>> Chris
>
cally it should halve the load and the close-emails don't really
> bring much benefit ;-)
>
> Chris
>
> Am 01.09.20, 16:26 schrieb "Dominik Riemer" :
>
> Hi all,
>
> currently, Jira notifications about created and closed issues are
> forwarded
>
09.2020 um 15:59 schrieb Dominik Riemer :
>>
>> Hi all,
>>
>> currently, Jira notifications about created and closed issues are forwarded
>> to the dev list, while all other Jira issues (e.g., comments or updates) are
>> sent to the iss...@streampipes.apache.org
Hi,
that is definitely the case - I myself had the same problems not really seeing
the discussion mails on the dev list.
So def a +1 for changing the settings.
Patrick
> Am 01.09.2020 um 15:59 schrieb Dominik Riemer :
>
> Hi all,
>
> currently, Jira notifications about cre
?
Theoretically it should halve the load and the close-emails don't really bring
much benefit ;-)
Chris
Am 01.09.20, 16:26 schrieb "Dominik Riemer" :
Hi all,
currently, Jira notifications about created and closed issues are forwarded
to the dev list, while all other Jira i
Hi all,
currently, Jira notifications about created and closed issues are forwarded
to the dev list, while all other Jira issues (e.g., comments or updates) are
sent to the iss...@streampipes.apache.org
<mailto:iss...@streampipes.apache.org> list.
My feeling is that the increasing
Hi,
Jira notifications are now configured (as you already might have noticed ;-))
The following scheme has been applied (copied from the INFRA response from
John):
Should be good now, for clarity I actually added dev@ to the following events
Issue Created
Issue Resolved
Issue Closed
Issue
Hi,
the mailing list iss...@streampipes.apache.org is created an I've filed an
Infra ticket to set up our Jira notifications.
Dominik
-Original Message-
From: Philipp Zehnder
Sent: Tuesday, December 10, 2019 8:09 AM
To: dev@streampipes.apache.org
Subject: Re: Jira notifications
Hi
Hi,
I also agree with Chris.
I think it makes sense to have the issues mailing list as well.
Philipp
> On 9. Dec 2019, at 19:44, Dominik Riemer wrote:
>
> Hi Chris,
>
> sounds good! (and nobody seems to have any objections)
> I looked up the corresponding PLC4X issue at
>
Hi Chris,
sounds good! (and nobody seems to have any objections)
I looked up the corresponding PLC4X issue at
https://issues.apache.org/jira/browse/INFRA-17923, which seems to describe the
approach. I can create the ticket.
Can you please create another mailing list
Hi,
> It would be also great if some mentors have a best-practice-hint here ;-)
It varies from project to project mostly due to the amount of traffic and how
it is used.
Thanks,
Justin
Hi,
it seems we can also decide how we would like to handle Jira notifications.
I can be configured which notifications are sent to project mailing lists
(e.g., when issues are updated or created).
I had a quick look how other projects have configured notifications, e.g.,
it seems that PLC4X
15 matches
Mail list logo
