Re: Dependabot emails are filling my mailbox
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 different emails. See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss Personally, I use GitHub notifications as it enables me to subscribe or mute issues/PRs individually, and I believe the only viable reason for having GitBox notifications is for archiving purposes (== write-only). b) Disable propagating PR comments to JIRA comments. See https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. That would resolve "PR comments are duplicated in JIRA" issue. Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub Issues, and Apache Lucene recently migrated from JIRA to GitHub Issues, so the migration is an option indeed. Vladimir
Re: Dependabot emails are filling my mailbox
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 Sitnikov > wrote: > > 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 different emails. > See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss > Personally, I use GitHub notifications as it enables me to subscribe or > mute issues/PRs individually, > and I believe the only viable reason for having GitBox notifications is for > archiving purposes (== write-only). > > b) Disable propagating PR comments to JIRA comments. > See > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions > > c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. > That would resolve "PR comments are duplicated in JIRA" issue. > Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub > Issues, and Apache Lucene > recently migrated from JIRA to GitHub Issues, so the migration is an option > indeed. > > Vladimir
Re: Dependabot emails are filling my mailbox
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, though nothing concrete yet. Guess I’ll file an Infra ticket about > the issue. > > — > Matt Sicker > >>> On Sep 25, 2022, at 04:16, Vladimir Sitnikov >>> wrote: >>> >> 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 different emails. >> See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss >> Personally, I use GitHub notifications as it enables me to subscribe or >> mute issues/PRs individually, >> and I believe the only viable reason for having GitBox notifications is for >> archiving purposes (== write-only). >> >> b) Disable propagating PR comments to JIRA comments. >> See >> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions >> >> c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. >> That would resolve "PR comments are duplicated in JIRA" issue. >> Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub >> Issues, and Apache Lucene >> recently migrated from JIRA to GitHub Issues, so the migration is an option >> indeed. >> >> Vladimir
Re: Dependabot emails are filling my mailbox
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 > message in my mailbox. I’ve already had to clear out several gigs of emails, > and these Dependabot rebases and relentless updates are making it impossible > to follow anything on the mailing lists anymore. > > Proposal: all Dependabot messages should be batched into a digest email or > similar. I don’t need multiple notifications per PR, and I don’t need dozens > of Jira issues commented on for no good reason. Alternative: disable > Dependabot as a failed experiment. > > — > Matt Sicker
Re: `logging-parent` release
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 can do it. It’s a > normal `mvn release:prepare release:publish` along with logging in yo > repository.apache.org to close the release and prepare as a release > candidate. Instructions are all on our Confluence page about it. > > — > Matt Sicker > >> On Sep 18, 2022, at 07:49, Piotr P. Karwasz wrote: >> >> Hi Ralph, >> >> On Sun, 18 Sept 2022 at 01:30, Ralph Goers >> wrote: >>> I would suggest that if you bump the logging parent to use it and then test >>> Log4j >>> with it and get a successful build then just do it. We don’t need to >>> discuss stuff like >>> this if it works. >> >> The upgrade required adding a couple of automatic module names to >> artifacts that didn't have them. >> Otherwise it passes the tests (also `./mvnw site`): >> https://github.com/apache/logging-log4j2/pull/1063 >> >> The builds are finally reproducible (I tested on the `log4j-api` JAR). >> >> Ralph, could you release `logging-parent` version 6? >> >> Piotr
[LAZY][VOTE] Release Logging parent pom version 7
[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: https://repository.apache.org/content/repositories/orgapachelogging-1090/ POM file: https://repository.apache.org/content/repositories/orgapachelogging-1090/org/apache/logging/logging-parent/7/logging-parent-7.pom All relevant files: - https://repository.apache.org/content/repositories/orgapachelogging-1090/org/apache/logging/logging-parent/7/logging-parent-7-source-release.zip - https://repository.apache.org/content/repositories/orgapachelogging-1090/org/apache/logging/logging-parent/7/logging-parent-7-source-release.zip.asc - https://repository.apache.org/content/repositories/orgapachelogging-1090/org/apache/logging/logging-parent/7/logging-parent-7-source-release.zip.sha512 - https://repository.apache.org/content/repositories/orgapachelogging-1090/org/apache/logging/logging-parent/7/logging-parent-7.pom - https://repository.apache.org/content/repositories/orgapachelogging-1090/org/apache/logging/logging-parent/7/logging-parent-7.pom.asc Git URL: https://gitbox.apache.org/repos/asf/logging-parent.git Tag: logging-parent-7 Keys file: https://downloads.apache.org/logging/KEYS Release signed with keyid 0x031EE010CA15D1EE If your copy of gpg cannot understand this signature format, let me know! I’ve been using this key for a while now, though. — Matt Sicker
