plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Mitsch <>
Subject Re: [DISCUSS] Send Jira emails to
Date Fri, 22 Feb 2019 08:29:30 GMT
I don’t know the amount of work that has to be spent on creating a new list for those kind
of notifications.
But with this project continouusly growing and growing maybe also ticket-count and stuff like
this will rise, so i can understand Otto concern.
If it’s possible (and could be done in a tolerable amount of time) i like the idea of splitting
mailing-list into dev-stuff (feature and discussions) and orga-stuff (issues,commits)


Von: Christofer Dutz <>
Datum: Freitag, 22. Februar 2019 um 09:14
An: "" <>, Tim Mitsch <>
Betreff: Re: [DISCUSS] Send Jira emails to

I think it's all a volume thing ... I agree that github code review emails in some projects
(Apache Commons) are super annoying, however do we only have a hand full of new issues per
month. Didn't think it's worth creating a dedicated List for that. And we can always create
it and redirect as soon as it starts really becoming annoying ... But what do the others think?
Rather create a separate list?
Outlook für Android<> herunterladen

From: Otto Fowler <>
Sent: Thursday, February 21, 2019 4:31:09 PM
To:; Tim Mitsch
Subject: Re: [DISCUSS] Send Jira emails to

-1 most projects have an issues@   list for this type of thing.
Dev lists that have build, jira, github stuff spamming them stink.

Does this incubator have:
setup or is it just dev@?

On February 21, 2019 at 06:22:52, Tim Mitsch ( wrote:


It would be good to be noticed.

Am 21.02.19, 11:32 schrieb "Christofer Dutz" <>:

Hi all,

today I noticed again that a user seems to have created an issue and we
didn’t get notified. I would like to have infra configure our project to
automatically send emails to the dev list …
If there are no objections, I would request this ASAP.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message