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 Reopened and issues@ to the rest. In case we're getting too many issue mails to the dev list, we can easily change the notification scheme. Dominik -----Original Message----- From: Dominik Riemer <[email protected]> Sent: Thursday, December 12, 2019 3:01 PM To: [email protected] Subject: RE: Jira notifications Hi, the mailing list [email protected] is created an I've filed an Infra ticket to set up our Jira notifications. Dominik -----Original Message----- From: Philipp Zehnder <[email protected]> Sent: Tuesday, December 10, 2019 8:09 AM To: [email protected] Subject: Re: Jira notifications 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 <[email protected]> wrote: > > 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 [email protected]? > > Dominik > > On 2019/12/08 10:20:14, Christofer Dutz <[email protected]> wrote: >> Hi all, >> >> I would personally suggest to have an issues@ mailinglist, where all >> notifications go to and additionally send create events to the dev list. >> I really don't like the template for the about line of these emails because >> you usually get to the important part after 3-4 prefixes. >> On my phone I just delete these emails because I don't want to click all of >> them through to find out what they are about. >> >> Having all notifications go to develop is, in my opinion, a bad idea. >> >> Chris >> >> >> Am 08.12.19, 00:50 schrieb "Justin Mclean" <[email protected]>: >> >> 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 >> >>
