Yes, master is behind. At some point, both master and release-2.x, especially master had build problems. When I could not build master I stopped porting changes which I had been doing all along for my 1.2 bridge changes. I just did not want to put in even more time into master when I had a lot left to do in release-2.x. So, that's how we got to where we are.
Gary Gary On Mon, Mar 21, 2022, 07:19 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? >
