[PR] Bump org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0 [logging-log4j-jmx-gui]

dependabot[bot] opened a new pull request, #3: URL: https://github.com/apache/logging-log4j-jmx-gui/pull/3 Bumps org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?depende

Re: [PR] Bump org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0 [logging-log4j-jmx-gui]

github-actions[bot] commented on PR #3: URL: https://github.com/apache/logging-log4j-jmx-gui/pull/3#issuecomment-1838104741 Changes are applied by CI in 3aeeafbbb80bba1542ed0a38261e79d6cb4d7b26 -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] Bump org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0 [logging-log4j-jmx-gui]

dependabot[bot] commented on PR #3: URL: https://github.com/apache/logging-log4j-jmx-gui/pull/3#issuecomment-1838104820 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor ver

Re: [PR] Bump org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0 [logging-log4j-jmx-gui]

github-actions[bot] closed pull request #3: Bump org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0 URL: https://github.com/apache/logging-log4j-jmx-gui/pull/3 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

Future release schedule

Hi all, Since we have a fast and easy release process now and a release does not require a free weekend any more, I think we should have a regular release schedule. Unless something exceptional happens (e.g. big bug that renders `log4j-jcl` unusable ;-) ), I would propose to: * have a patch rel

Re: Future release schedule

Hi Piotr, I think scheduled releases that everybody can follow are great and your proposal makes sense. Does this also mean we don't have that many "noise" emails from upgraded dependency (releases)? I have come to realize in the past months that "inclusion" is most important, and that would

Re: Future release schedule

>From a user perspective, sometimes having releases too often leads to upgrade fatigue. Eventually it becomes easier to not upgrade, because so many things have changed in the interim that it becomes very annoying to attempt to upgrade things. For comparison, Ubuntu will do releases every 6 month

Re: Future release schedule

Even though you probably all know, just for clarity our policy has been that every release is a patch release until it isn’t. That is, as soon as something other than a bug fix is added it becomes a minor release. Personally, I think this still makes sense as it avoids needing the extra branch.