The system is setup now and the new issues@ list is alive and ready to
get new subscribers.
https://lists.apache.org/list.html?iss...@avro.apache.org
For info the current setup is:
- New/Merge/Close Github PR notifications go to dev@
- All other github interaction (mostly comments) go to issues@
I'd like a issues@avro or notifications@avro that has the detailed
messages from Github and Jira. Great suggestion.
I would prefer PR and jira issue creation / closure still go to the dev
list, but I don't feel strongly about it since I will probably subscribe to
both lists.
On Thu, May 7, 2020
Yes, I'd be in favor of having a separate ML. If you want to keep track of
the action at the repository, you can also get notified using Github.
Cheers, Fokko
Op do 7 mei 2020 om 14:37 schreef Ismaël Mejía :
> Let's wait for others opinions and if we agree I will proceed to
> create the ML next
Let's wait for others opinions and if we agree I will proceed to
create the ML next week.
On Thu, May 7, 2020 at 12:13 PM Ryan Skraba wrote:
>
> I think it's safe to create issues@ and merge the PR right away -- it
> would pretty much restore the behaviour the dev@ list had at the
> beginning of
I think it's safe to create issues@ and merge the PR right away -- it
would pretty much restore the behaviour the dev@ list had at the
beginning of the year.
I have all my mailing lists dumped into the same folder, but if
issues@ existed for JIRA and Github notifications, I would be tempted
to
Other alternative (probably the cleanest is to let dev@ only for
discussion and issues for all the JIRA/github action. The tradeoff
there is that people subscribed to dev@ only may miss part of the
action (+ it is not backwards compatible with our archives) but it is
clearly an option too.
On
The issues in the yaml file are every comment done on every issue or
pull requests on github (notice that the issues part probably won't
apply to us since we use JIRA to track issues).
Currently we receive ALL JIRA notifications into dev@ we can change
that us well since it probably makes
This sounds good to me! The "issues" in the yaml are the GitHub
issues, which are disabled in github right?
Any opinions on moving JIRA notifications from j...@apache.org to
issues@ as well? That's what I would expect!
I guess this would make little difference to me in practice since I
would
Hi Ismaël,
Yep, I think it's a little bit noisy for our mailing list with such
notifications. But it's fun to see what other people are working on.
IMHO, in addition to a new mailing list, we should have a better label
mechanism for easily routing/filtering messages.
Thank you.
On
Hello,
Some of you have probably noticed that we are receiving a LOT of extra
notifications that were not active in the past. This is happening because
Apache INFRA installed a new way to map notifications into mailing lists for its
projects and the default configuration right now is sending all
10 matches
Mail list logo
