rgoers commented on pull request #61: URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-666657635
Is there a tag included in the PR with the version number? Can those even be added in a PR. If not it is a simple matter to tag the version associated with this I guess. Yes, I sympathize with your predicament as you are in sort of a catch-22 at the moment. Yes, if you feel the release is ready for a vote start a vote thread with a subject of something like "[VOTE] Release Log4Net x.y.z". Please include in the vote thread the links to the artifacts to be reviewed. If you look at https://lists.apache.org/thread.html/r98e0c907521107b8da0de59978781bfbca9e82bfd97a7a87284c5a66%40%3Cdev.logging.apache.org%3E you will see an example of the latest vote thread for Log4j, but note that the only thing that is required is where to find what is to be voted on. For example, Log4j updates its web site with each release. That is not required but obviously the web site will want to describe how to get the latest artifacts. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
