>So I am happy you agree to say that it involves PMC, whatever the time it >takes.
If PMC can't allocate a minimal time for the release, they SHOULD be willing to transfer rights to the people who have more time. >If I may correct your formulation My formulation is: If somebody chimes in and does the heavy lifting for fixing JMeter 2.x, I would be OK to help with pushing the release, or I would be OK to transfer rights for 2.x to the given team if I can't help with the release. No way I would say something like "2.x is EOL, contributions unwelcome". No way I would say something like "please provide all the patches before I even consider the request" >What is being blocked here ? Please clarify ? >Are you speaking about: > - releasing JMeter 3.X with log4j2 updated ? I am speaking about "releasing JMeter 3.x with log4j2 updated". Here's the case once again: Vladimir>Supposed someone chimes in and suggest releasing JMeter 3.x Vladimir>with log4j fixed. Suppose they would be open to do 90% of all the heavy-lifting. Vladimir>For instance, they might suggest a PR to make JMeter 3 buildable, they act as a release manager, etc. Vladimir>Would you be open to just allowing the release to happen and voting on the release? I believe there's nothing to consider there, and we could (should) welcome that. I believe that behavior would be great for the community, and it would highlight JMeter in a positive light. Vladimir
