vy commented on PR #3852: URL: https://github.com/apache/logging-log4j2/pull/3852#issuecomment-3159747411
> *consistently* performing one of these actions *before* merging any PR to `2.x` I understand the motivation for keeping `main` in sync. with `2.x`. Given `main` will soon be released as Log4j 3 since... 2018-01-30 (041fe8ff) and we can hardly afford time for `2.x` maintenance, I am afraid of jeopardizing the Log4j 2 development by introducing a process that blocks `2.x` fixes for the sake of `main`. 1. @jvz, @ppkarwasz, do you have capacity to make significant commitment to Log4j 3 development once it is out? 2. If yes, can we introduce a process that does not block `2.x` development? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
