There are lots of commits in 2.x that need to be ported to master. Now that I've mostly finished the DI epic, I was thinking of working on auditing 2.x commits to make sure they're in master, though I'd hope that each of us can do that in modules we're familiar with.
On Mon, Mar 21, 2022 at 6:19 AM Volkan Yazıcı <vol...@yazi.ci> wrote: > > Gary and Piotr put a great deal of effort into `log4j-1.2-api` in > `release-2.x`. So far we haven't heard of any major complaints but happy > migration stories. Great job! 💯 > > While trying to cherry-pick a one-liner from `release-2.x` to `master` > today, I have run into some issues. If I am not mistaken, `log4j-1.2-api` > lags behind quite a bit in `master` compared to `release-2.x`. Is this > intentional? If not, do we have any plans to sync the two?
