vlsi commented on pull request #608: URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-993457975
> approach the Apache Software Foundation That is exactly what I am doing. > How does "unpaid volunteer" sound? ;-) @garydgregory , I am a committer and a PMC member on Apache Calcite and Apache JMeter. That is why I truly do not understand why it is that hard to roll 1.2.18 out. I know there's "dist.apache.org, voting, site update, announce, etc" overheads. I understand why do you want to stop bugfixes and features for 1.x branch, however, I believe this case is special, and it does not really take significant effort to remove several `.java` files. Do you suggest log4j PMC should be paid $5000 for each +1 vote regarding 1.2.18? I can prepare PR for the removal of the offending classes. That is a non-issue. However, only log4j PMCs can vote and make the release happen. Of course, I can fork log4j and publish it under new groupid:artifactid coordinates, however, it would look really weird, and Dependabot won't know that my log4j is a solution to the known issues. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org