+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (10.0.2): ok
- mvn clean apache-rat:check
* Built from source (10.0.2): ok
- mvn clean install -DskipTests
* Unit tests pass (10.0.2): ok
- mvn package -P runAllTests -Dsurefire.rerunFailingTestsCount=3
....
[INFO] Apache Hadoop Cloud Storage Project ................ SUCCESS [
0.026 s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 12:51 h
[INFO] Finished at: 2022-05-12T06:25:19-07:00
[INFO]
------------------------------------------------------------------------
[WARNING] The requested profile "runAllTests" could not be activated
because it does not exist.
Built a downstreamer against this RC and ran it in-the-small. Seemed fine.
S
On Wed, May 11, 2022 at 10:25 AM Steve Loughran <ste...@cloudera.com.invalid>
wrote:
> I have put together a release candidate (RC1) for Hadoop 3.3.3
>
> The RC is available at:
> https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC1/
>
> The git tag is release-3.3.3-RC1, commit d37586cbda3
>
> The maven artifacts are staged at
> https://repository.apache.org/content/repositories/orgapachehadoop-1349/
>
> You can find my public key at:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>
> Change log
> https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC1/CHANGELOG.md
>
> Release notes
> https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC1/RELEASENOTES.md
>
> There's a very small number of changes, primarily critical code/packaging
> issues and security fixes.
>
> * The critical fixes which shipped in the 3.2.3 release.
> * CVEs in our code and dependencies
> * Shaded client packaging issues.
> * A switch from log4j to reload4j
>
> reload4j is an active fork of the log4j 1.17 library with the classes
> which contain CVEs removed. Even though hadoop never used those classes,
> they regularly raised alerts on security scans and concen from users.
> Switching to the forked project allows us to ship a secure logging
> framework. It will complicate the builds of downstream
> maven/ivy/gradle projects which exclude our log4j artifacts, as they
> need to cut the new dependency instead/as well.
>
> See the release notes for details.
>
> This is the second release attempt. It is the same git commit as before,
> but
> fully recompiled with another republish to maven staging, which has bee
> verified by building spark, as well as a minimal test project.
>
> Please try the release and vote. The vote will run for 5 days.
>
> -Steve
>
