I fixed some rat errors, but yeah, looks like I missed that. I’ll cancel this 
and roll a third RC.

—
Matt Sicker

> On Dec 20, 2021, at 20:43, Raman Gupta <[email protected]> wrote:
> 
> As far as I can tell nothing has changed? Did you mean to point to 2.17.0?
> 
>> On Sun, Dec 19, 2021 at 5:52 PM Matt Sicker <[email protected]> wrote:
>> 
>> This is a vote to release Log4j Kotlin API version 1.2.0, the next version
>> of the Kotlin facade for Log4j2.
>> 
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>> 
>> The vote will remain open for 72 hours (or more if required). All votes
>> are welcome and we encourage everyone to test the release, but only Logging
>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>> positive than negative votes are required.
>> 
>> Changes in this release include:
>> 
>> * LOG4J2-3218: Update Log4j dependency to 2.16.0.
>> 
>> This is primarily provided to help upgrade transitive dependencies on
>> log4j-core which was recently updated to fix CVE-2021-44228 and
>> CVE-2021-45046.
>> 
>> Tag:
>> a)  for a new copy do "git clone
>> https://github.com/apache/logging-log4j-kotlin.git” and then "git
>> checkout tags/log4j-api-kotlin-1.2.0-rc2”  or just "git clone -b
>> log4j-api-kotlin-1.2.0-rc2
>> https://github.com/apache/logging-log4j-kotlin.git";
>> b) for an existing working copy to “git pull” and then “git checkout
>> tags/log4j-api-kotlin-1.2.0-rc2”
>> 
>> Web Site: https://logging.staged.apache.org/log4j/kotlin/index.html
>> 
>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachelogging-1073/
>> 
>> Distribution archives:
>> https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/
>> 
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>> https://repository.apache.org/content/repositories/orgapachelogging-1073/org/apache/logging/log4j/
>> 
>> --
>> Matt Sicker
>> 
>> 

Reply via email to