Alternative options could be:
a) Divert GitBox notifications to a separate mailing list (e.g.
issues-gitbox@) which no one really subscribes.
The key issue with GitBox notifications is that it produces messages that
do not group by subject,
so 5 notifications on a single PR might look like 5 diffe
I tried disabling Jira propagation before via that file, though it still seems
to be enabled. We have talked a little before about migrating to GitHub Issues,
though nothing concrete yet. Guess I’ll file an Infra ticket about the issue.
—
Matt Sicker
> On Sep 25, 2022, at 04:16, Vladimir Sitnik
Just filed https://issues.apache.org/jira/browse/INFRA-23722
—
Matt Sicker
> On Sep 25, 2022, at 11:12, Matt Sicker wrote:
>
> I tried disabling Jira propagation before via that file, though it still
> seems to be enabled. We have talked a little before about migrating to GitHub
> Issues, th
Alright, I found the setting related to this and disabled it. Hopefully this
will address most of the Dependabot noise and make the tool useful again!
—
Matt Sicker
> On Sep 23, 2022, at 18:46, Matt Sicker wrote:
>
> After secretary emails, emails related to Dependabot are the next most common
I should note that the docs in
https://cwiki.apache.org/confluence/display/LOGGING/Logging+Parent+POM+Release+Guide
are fairly comprehensive. I’m doing a release right now.
—
Matt Sicker
> On Sep 18, 2022, at 11:24, Matt Sicker wrote:
>
> Normally I take care of that, though anyone on the PMC
[Note that version 6 was skipped due to some fumbling on my part and an
inability to rewrite history once mvn did a git push, hence version 7.]
This is a lazy vote to release logging-parent 7. This vote is open for 72 hours
and will pass unless getting a net negative vote count.
Staging repo:
h
