Thanks for driving the release, Steve and Mukund. I found that there were some jiras with wrong fix versions.
The fix versions included 3.3.5, but actually, it isn't in 3.3.5-RC1: - HDFS-16845 - HADOOP-18345 The fix versions didn't include 3.3.5, but actually, it is in 3.3.5-RC1 (and it is not in release-3.3.4) : - HADOOP-17276 - HDFS-13293 - HDFS-15630 - HDFS-16266 - HADOOP-18003 - HDFS-16310 - HADOOP-18014 I corrected all the wrong fix versions just now. I'm not sure we should revote it since it only affects the changelog. - Takanobu 2023年2月21日(火) 22:43 Steve Loughran <ste...@cloudera.com.invalid>: > Apache Hadoop 3.3.5 > > Mukund and I have put together a release candidate (RC1) for Hadoop 3.3.5. > > What we would like is for anyone who can to verify the tarballs, especially > anyone who can try the arm64 binaries as we want to include them too. > > The RC is available at: > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.5-RC1/ > > The git tag is release-3.3.5-RC1, commit 274f91a3259 > > The maven artifacts are staged at > https://repository.apache.org/content/repositories/orgapachehadoop-1368/ > > 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/hadoop-3.3.5-RC1/CHANGELOG.md > > Release notes > > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.5-RC1/RELEASENOTES.md > > This is off branch-3.3 and is the first big release since 3.3.2. > > Key changes include > > * Big update of dependencies to try and keep those reports of > transitive CVEs under control -both genuine and false positives. > * HDFS RBF enhancements > * Critical fix to ABFS input stream prefetching for correct reading. > * Vectored IO API for all FSDataInputStream implementations, with > high-performance versions for file:// and s3a:// filesystems. > file:// through java native io > s3a:// parallel GET requests. > * This release includes Arm64 binaries. Please can anyone with > compatible systems validate these. > > Note, because the arm64 binaries are built separately on a different > platform and JVM, their jar files may not match those of the x86 > release -and therefore the maven artifacts. I don't think this is > an issue (the ASF actually releases source tarballs, the binaries are > there for help only, though with the maven repo that's a bit blurred). > > The only way to be consistent would actually untar the x86.tar.gz, > overwrite its binaries with the arm stuff, retar, sign and push out > for the vote. Even automating that would be risky. > > Please try the release and vote. The vote will run for 5 days. > > Steve and Mukund >
