You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by Chris Nauroth <cn...@apache.org> on 2026/01/26 23:23:05 UTC
Apache Hadoop 3.5.0 release candidates
Hello everyone,
I'm happy to report that I've done a successful dry run of creating a 3.5.0
release candidate from the trunk branch, with a few additional patches
applied locally. I plan to proceed with the full release process as soon as
we resolve the following blockers:
HADOOP-19785 <https://issues.apache.org/jira/browse/HADOOP-19785>: mvn site
fails in JDK17
HADOOP-19790 <https://issues.apache.org/jira/browse/HADOOP-19790>: Build
Failing on Trunk
HADOOP-19794 <https://issues.apache.org/jira/browse/HADOOP-19794>:
create-release
version parsing incompatible with Java 17
The first of these is the most challenging IMO. There are competing
proposals to either 1) switch to some selective maven-javadoc-plugin
filtering, or 2) explore additional manipulations of internal JDK APIs to
keep our annotation-based visibility mechanism working. I'd appreciate any
additional contributor help here to unblock the release.
The second looks like we need a fairly trivial update to documentation and
pom.xml files to require a compatible Maven version. I can look into
helping with this.
The third just needs a one-line patch in the release script, for which I've
already sent a pull request.
Additionally, I have never done the ARM release, so I could use a little
help understanding that. From what I can tell, it's a matter of following
the main release wiki...
https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease
...and then following instructions from the hadoop-release-support repo to
add ARM binaries:
https://github.com/apache/hadoop-release-support?tab=readme-ov-file#building-arm64-binaries
Does that sound right at a high level? Let me know if I'm missing something.
We're getting close!
Chris Nauroth
Re: Apache Hadoop 3.5.0 release candidates
Posted by Steve Loughran <st...@cloudera.com>.
On Mon, 26 Jan 2026 at 23:23, Chris Nauroth <cn...@apache.org> wrote:
> Hello everyone,
>
> I'm happy to report that I've done a successful dry run of creating a 3.5.0
> release candidate from the trunk branch, with a few additional patches
> applied locally. I plan to proceed with the full release process as soon as
> we resolve the following blockers:
>
Awesome!
>
> HADOOP-19785 <https://issues.apache.org/jira/browse/HADOOP-19785>: mvn
> site
> fails in JDK17
> HADOOP-19790 <https://issues.apache.org/jira/browse/HADOOP-19790>: Build
> Failing on Trunk
> HADOOP-19794 <https://issues.apache.org/jira/browse/HADOOP-19794>:
> create-release
> version parsing incompatible with Java 17
>
> The first of these is the most challenging IMO. There are competing
> proposals to either 1) switch to some selective maven-javadoc-plugin
> filtering, or 2) explore additional manipulations of internal JDK APIs to
> keep our annotation-based visibility mechanism working. I'd appreciate any
> additional contributor help here to unblock the release.
>
no idea there I"m afraid.
>
> The second looks like we need a fairly trivial update to documentation and
> pom.xml files to require a compatible Maven version. I can look into
> helping with this.
>
> The third just needs a one-line patch in the release script, for which I've
> already sent a pull request.
>
> Additionally, I have never done the ARM release, so I could use a little
> help understanding that. From what I can tell, it's a matter of following
> the main release wiki...
>
> https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease
>
> ...and then following instructions from the hadoop-release-support repo to
> add ARM binaries:
>
>
> https://github.com/apache/hadoop-release-support?tab=readme-ov-file#building-arm64-binaries
>
> Does that sound right at a high level? Let me know if I'm missing
> something.
>
I've just pushed out an update to that repo, the ant targets to scp down
the binary tar from an arm system, after which
the copy with rename and sign is similar to a local build.
Only do a -asfrelease or -deploy with one of the builds; because of all the
network pain I did it with the arm one this time. Which means that the jars
in the mvn repo will match that release, not the x86. Welcome to the future.
Email me directly if you want some more assistance there.
Re: Apache Hadoop 3.5.0 release candidates
Posted by Steve Loughran <st...@cloudera.com>.
On Mon, 26 Jan 2026 at 23:23, Chris Nauroth <cn...@apache.org> wrote:
> Hello everyone,
>
> I'm happy to report that I've done a successful dry run of creating a 3.5.0
> release candidate from the trunk branch, with a few additional patches
> applied locally. I plan to proceed with the full release process as soon as
> we resolve the following blockers:
>
Awesome!
>
> HADOOP-19785 <https://issues.apache.org/jira/browse/HADOOP-19785>: mvn
> site
> fails in JDK17
> HADOOP-19790 <https://issues.apache.org/jira/browse/HADOOP-19790>: Build
> Failing on Trunk
> HADOOP-19794 <https://issues.apache.org/jira/browse/HADOOP-19794>:
> create-release
> version parsing incompatible with Java 17
>
> The first of these is the most challenging IMO. There are competing
> proposals to either 1) switch to some selective maven-javadoc-plugin
> filtering, or 2) explore additional manipulations of internal JDK APIs to
> keep our annotation-based visibility mechanism working. I'd appreciate any
> additional contributor help here to unblock the release.
>
no idea there I"m afraid.
>
> The second looks like we need a fairly trivial update to documentation and
> pom.xml files to require a compatible Maven version. I can look into
> helping with this.
>
> The third just needs a one-line patch in the release script, for which I've
> already sent a pull request.
>
> Additionally, I have never done the ARM release, so I could use a little
> help understanding that. From what I can tell, it's a matter of following
> the main release wiki...
>
> https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease
>
> ...and then following instructions from the hadoop-release-support repo to
> add ARM binaries:
>
>
> https://github.com/apache/hadoop-release-support?tab=readme-ov-file#building-arm64-binaries
>
> Does that sound right at a high level? Let me know if I'm missing
> something.
>
I've just pushed out an update to that repo, the ant targets to scp down
the binary tar from an arm system, after which
the copy with rename and sign is similar to a local build.
Only do a -asfrelease or -deploy with one of the builds; because of all the
network pain I did it with the arm one this time. Which means that the jars
in the mvn repo will match that release, not the x86. Welcome to the future.
Email me directly if you want some more assistance there.
Re: Apache Hadoop 3.5.0 release candidates
Posted by Steve Loughran <st...@cloudera.com>.
On Mon, 26 Jan 2026 at 23:23, Chris Nauroth <cn...@apache.org> wrote:
> Hello everyone,
>
> I'm happy to report that I've done a successful dry run of creating a 3.5.0
> release candidate from the trunk branch, with a few additional patches
> applied locally. I plan to proceed with the full release process as soon as
> we resolve the following blockers:
>
Awesome!
>
> HADOOP-19785 <https://issues.apache.org/jira/browse/HADOOP-19785>: mvn
> site
> fails in JDK17
> HADOOP-19790 <https://issues.apache.org/jira/browse/HADOOP-19790>: Build
> Failing on Trunk
> HADOOP-19794 <https://issues.apache.org/jira/browse/HADOOP-19794>:
> create-release
> version parsing incompatible with Java 17
>
> The first of these is the most challenging IMO. There are competing
> proposals to either 1) switch to some selective maven-javadoc-plugin
> filtering, or 2) explore additional manipulations of internal JDK APIs to
> keep our annotation-based visibility mechanism working. I'd appreciate any
> additional contributor help here to unblock the release.
>
no idea there I"m afraid.
>
> The second looks like we need a fairly trivial update to documentation and
> pom.xml files to require a compatible Maven version. I can look into
> helping with this.
>
> The third just needs a one-line patch in the release script, for which I've
> already sent a pull request.
>
> Additionally, I have never done the ARM release, so I could use a little
> help understanding that. From what I can tell, it's a matter of following
> the main release wiki...
>
> https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease
>
> ...and then following instructions from the hadoop-release-support repo to
> add ARM binaries:
>
>
> https://github.com/apache/hadoop-release-support?tab=readme-ov-file#building-arm64-binaries
>
> Does that sound right at a high level? Let me know if I'm missing
> something.
>
I've just pushed out an update to that repo, the ant targets to scp down
the binary tar from an arm system, after which
the copy with rename and sign is similar to a local build.
Only do a -asfrelease or -deploy with one of the builds; because of all the
network pain I did it with the arm one this time. Which means that the jars
in the mvn repo will match that release, not the x86. Welcome to the future.
Email me directly if you want some more assistance there.
Re: Apache Hadoop 3.5.0 release candidates
Posted by Steve Loughran <st...@cloudera.com>.
On Mon, 26 Jan 2026 at 23:23, Chris Nauroth <cn...@apache.org> wrote:
> Hello everyone,
>
> I'm happy to report that I've done a successful dry run of creating a 3.5.0
> release candidate from the trunk branch, with a few additional patches
> applied locally. I plan to proceed with the full release process as soon as
> we resolve the following blockers:
>
Awesome!
>
> HADOOP-19785 <https://issues.apache.org/jira/browse/HADOOP-19785>: mvn
> site
> fails in JDK17
> HADOOP-19790 <https://issues.apache.org/jira/browse/HADOOP-19790>: Build
> Failing on Trunk
> HADOOP-19794 <https://issues.apache.org/jira/browse/HADOOP-19794>:
> create-release
> version parsing incompatible with Java 17
>
> The first of these is the most challenging IMO. There are competing
> proposals to either 1) switch to some selective maven-javadoc-plugin
> filtering, or 2) explore additional manipulations of internal JDK APIs to
> keep our annotation-based visibility mechanism working. I'd appreciate any
> additional contributor help here to unblock the release.
>
no idea there I"m afraid.
>
> The second looks like we need a fairly trivial update to documentation and
> pom.xml files to require a compatible Maven version. I can look into
> helping with this.
>
> The third just needs a one-line patch in the release script, for which I've
> already sent a pull request.
>
> Additionally, I have never done the ARM release, so I could use a little
> help understanding that. From what I can tell, it's a matter of following
> the main release wiki...
>
> https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease
>
> ...and then following instructions from the hadoop-release-support repo to
> add ARM binaries:
>
>
> https://github.com/apache/hadoop-release-support?tab=readme-ov-file#building-arm64-binaries
>
> Does that sound right at a high level? Let me know if I'm missing
> something.
>
I've just pushed out an update to that repo, the ant targets to scp down
the binary tar from an arm system, after which
the copy with rename and sign is similar to a local build.
Only do a -asfrelease or -deploy with one of the builds; because of all the
network pain I did it with the arm one this time. Which means that the jars
in the mvn repo will match that release, not the x86. Welcome to the future.
Email me directly if you want some more assistance there.