Have you looked at the `Closed` tab? See #3789 <https://github.com/apache/logging-log4j2/pull/3789>, #3775 <https://github.com/apache/logging-log4j2/issues/3775>, #3968 <https://github.com/apache/logging-log4j2/pull/3968>, etc.
On Tue, Apr 28, 2026 at 11:49 PM Gary Gregory <[email protected]> wrote: > On Tue, Apr 28, 2026 at 5:45 PM Volkan Yazıcı <[email protected]> wrote: > > > > I've walked through the entire `rel/2.25.0..2.x` commit list and > prepared the > > `2.26.0` milestone < > https://github.com/apache/logging-log4j2/milestone/22> > > Hi All, > > I don't see any new features that would warrant a minor version bump, > just bug fixes, so not use a 2.25.x label? > > Gary > > > for your view. See that this milestone still has some open issues. I've > > nudged some of the contributors to respond to reviews and bring the PR to > > the finish line so that it can be delivered in `2.26.0`. I will wait > for a > > day or two for reactions, and fork the `release/2.26.0` branch from then > > on. I will move the left over issues to the `2.x` milestone. > > > > On Wed, Apr 15, 2026 at 1:40 PM Piotr P. Karwasz < > [email protected]> > > wrote: > > > > > Hi Volkan, > > > > > > On 15.04.2026 09:49, Volkan Yazıcı wrote: > > > > I want to release `2.26.0` in a week or two, plus 1 week for the > release > > > > process. > > > > > > > > See the `2.26.0` milestone on GitHub: > > > > https://github.com/apache/logging-log4j2/milestone/22 > > > > > > > > > Thanks for doing this. If you have time, can you make a short summary > of > > > the main features we want to deliver in `2.26.0`? If I remember > > > correctly, there was a bunch of changes related to throwable formatting > > > and we certainly want to change the defaults for TLS verification. > > > Anything else? > > > > > > A partial migration to NIO has been started and I think we are only one > > > PR short of delivering it (I must have a local branch for that). > > > > > > > Since `2.25.4` PRs (IMO, unfortunately) targeted the branch `2.25.x` > > > > instead of first targeting `2.x` and then getting cherry-picked from > > > `2.x` > > > > to `2.25.x`, those changes don't appear on the `2.26.0` milestone. > Hence, > > > > for those, you need to include the `2.25.4` milestone changes > > > > <https://github.com/apache/logging-log4j2/milestone/25> too. I will > > > land a > > > > PR copying `src/changelog/2.25.4` contents to `src/changelog/.2.x.x`. > > > > > > > > > Why would you want to duplicate the changes in `2.25.4`? They were > > > delivered before the first 2.26.x version was released, so normally you > > > assume they must be there. > > > > > > Piotr > > > >
