This vote has passed with binding +1 votes from Remko Popma, Matt Sicker, Gary
Gregory, Carter Kozak, Volkan Yazici, and Ralph Goers. Duo Zhang also voted +1.
I will continue with the release process.
Ralph
My +1
Ralph
> On Feb 23, 2022, at 4:58 PM, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.17.2, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
+1
*What did I check?*
`./mvnw verify -Dmaven.soap.skip` succeeds.
Checked `./mvnw site -N -DskipTests`, spotted the same issues Matt noted.
`bin/verify-release-artifacts.sh` succeeds. (Who wrote this awesome script?)
Checked against our in-house Log4j wrapper at bol.com, tests passed.
*What did
+1
Build is green.
Validated the artifacts across a variety projects I maintain, tests are all
green.
A few builder 'with' methods failed in builds that lint against deprecation due
to new overloads with 'set' methods.
Also tested spring-boot from commit 8a7e40ce918759a5936d19341077ff15410afe17
+1
Based on the src zip:
- SHA-512 OK
- ASC OK
- RAT check OK
- mvn clean install only works by skipping the Cassandra module on macOS
- Above mvn build OK on Windows 10
Tested on macOS with a toolchain:
Darwin ***.local 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58
PST 2022; root:xnu
Note that it may be necessary to use -Drevapi.skip=true to build. The plugin
seems to fail in different places on different machines or even on the same
machine running different maven goals.
Ralph
> On Feb 23, 2022, at 4:58 PM, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.17.2, t
+1(non-binding)
I opened a PR in hbase to make use of the staging artifacts
https://github.com/apache/hbase/pull/4096
I tried to compile and dist locally, all looked good.
Started a standalone mini cluster of hbase, used the newly introduced
syntax in LOG4J2-3341 to specify level and appender a
Version 2.12.4 is still in the dist folder for some reason, which I
accidentally downloaded and built instead of what we are actually
validating, doh, bad on me.
Gary
On Wed, Feb 23, 2022 at 6:58 PM Ralph Goers
wrote:
> This is a vote to release Log4j 2.17.2, the next version of the Log4j 2
> p
I will take a look. I had thought I verified they had 2 spaces.
Ralph
> On Feb 23, 2022, at 7:54 PM, Remko Popma wrote:
>
> I noted that the checksum files for the distribution archives are now
> _almost_ in the right format to allow checking with the `shasum` utility:
>
> cat ./apache-log4j-
+1
Build good, sigs good, artifacts good.
Site notes:
* Markdown parsing errors on homepage with “##” instead of tags or
whatever goes there.
* API Separation page has an outdated version reference
* Similar markdown parsing errors on the Log4j 1.x Migration page with “”
being left as-is.
I noted that the checksum files for the distribution archives are now
_almost_ in the right format to allow checking with the `shasum` utility:
cat ./apache-log4j-2.17.2-bin.tar.gz.sha256
c8f7cfe4ac9825043432b310709dee2661398573de28c83e603e80e0e86df9bb
apache-log4j-2.17.2-bin.tar.gz
Unfortunately
+1
Signatures good, checksums good.
Build passes (ignoring rev-api problem for the mongodb3 module)
Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
2019-08-28T00:06:16+09:00)
Maven home: C:\apps\apache-maven-3.6.2\bin\..
Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:
This is a vote to release Log4j 2.17.2, the next version of the Log4j 2 project.
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. All votes are welcome and we encourage
ev
13 matches
Mail list logo
