This is an automated email from the ASF dual-hosted git repository.
stevel pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/hadoop-release-support.git
The following commit(s) were added to refs/heads/main by this push:
new a6f7dbf HADOOP-19770 3.4.3 RC1
a6f7dbf is described below
commit a6f7dbfa439ee3f97f12654550332c24f916cc66
Author: Steve Loughran <[email protected]>
AuthorDate: Tue Feb 17 10:31:29 2026 +0000
HADOOP-19770 3.4.3 RC1
---
README.md | 42 +++++++++++++++++++++++-------
build.xml | 30 ++++++++++++---------
src/releases/release-info-3.4.3.properties | 6 ++---
src/text/vote.txt | 4 ---
4 files changed, 53 insertions(+), 29 deletions(-)
diff --git a/README.md b/README.md
index b845983..5cbcd82 100644
--- a/README.md
+++ b/README.md
@@ -224,6 +224,9 @@ gpg --import gpg_public
gpg --import private.key
````
+
+### Create the release with the `create-release` script
+
Follow rest of process as mentioned in above HowToRelease doc.
```sh
@@ -231,7 +234,7 @@ git clone https://github.com/apache/hadoop.git
cd hadoop
git checkout --track origin/branch-3.4.3
-# for the arm buld: dev-support/bin/create-release --docker --dockercache
+# for the arm buld, see the sepaate section.
dev-support/bin/create-release --asfrelease --docker --dockercache
```
@@ -295,7 +298,6 @@ ant clean mvn-purge
Tip: look at the output to make sure it is cleaning the artifacts from the
release you intend to validate.
-
### SCP the RC down to `target/incoming`
This will take a while! look in target/incoming for progress
@@ -442,6 +444,13 @@ of the build.
```
[gpg] gpg: using "38237EE425050285077DB57AD22CF846DBB162A0" as default secret
key for signing
```
+
+After this, renamed -aarch64 files will be in the release dir
+
+```
+nt release.dir.check
+```
+
### Publishing the RC
Publish the RC by copying it to a staging location in the hadoop SVN
repository.
@@ -584,7 +593,7 @@ locally.
# How to download and build a staged release candidate
-This project can be used to download and validated a release created by other
people,
+This project can be used to download and validate a release staged on the
apache distribution site,
downloading the staged artifacts and validating their signatures before
executing some (minimal) commands.
@@ -643,13 +652,13 @@ This will import all the KEYS from
then verify the signature of each downloaded file.
If you don't yet trust the key of whoever signed the release then
-1. Refresh the keys from the OpenPGP server, to see
- if they've been signed by others.
+Refresh the keys from the OpenPGP server, to see if they've been
+signed by others.
gpg --refresh-keys
-2. Perform whatever key verification you can and sign the key that
- level -ideally push up the signature to the servers.
+Perform whatever key verification you can and sign the key that
+level -ideally push up the signature to the servers.
### Untar source and build
@@ -742,9 +751,9 @@ auth-keys.xml=/home/alice/private/xml/auth-keys.xml
```
-## Testing ARM binaries
+## Testing Staged ARM binaries
-There are ARM variants of the commands to fetch and validate the ARM binaries.
+There are ARM variants of the commands to fetch and validate staged ARM
binaries.
| target | action
|
|-------------------------|------------------------------------------------------------|
@@ -755,6 +764,7 @@ There are ARM variants of the commands to fetch and
validate the ARM binaries.
```bash
# untars the `-aarch64.tar.gz` binary
+ant mvn-test
ant release.fetch.arm gpg.arm.verify
ant release.arm.untar
ant release.arm.commands
@@ -778,7 +788,7 @@ For this to work:
1. Check out the relevant projects in your local system.
2. Set their location in the `build.properties` file
-3. Make sure that the branch checked out is the one you want to build.
+3. Make sure the branch checked out is the one you want to build.
This matters for anyone who works on those other projects
on their own branches.
4. Some projects need java11 or later.
@@ -1178,6 +1188,18 @@ ant stage-svn-rollback
ant stage-svn-log
```
+Go to the release-info properties file for the release and
+
+
+comment out the following fields (stops you forgetting to update them)
+```
+amd.src.dir
+asf.staging.url
+git.commit.id
+```
+
+For the `rc` property: increment it.
+
# Releasing Hadoop-thirdparty
diff --git a/build.xml b/build.xml
index 28b4d71..2cbf65c 100644
--- a/build.xml
+++ b/build.xml
@@ -1252,21 +1252,26 @@ Message is in file ${message.out}
<arg value="file://${target}" />
</hadoop>
- <echo>s3guard help</echo>
+ <echo>Locating a class in hadoop-azure JAR</echo>
<hadoop>
- <arg value="s3guard" />
- <arg value="help" />
+ <arg value="${findclass}" />
+ <arg value="load" />
+ <arg value="org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem" />
</hadoop>
- <echo>findclass azure</echo>
+ <echo>Locating a class in hadoop-aws JAR</echo>
<hadoop>
<arg value="${findclass}" />
<arg value="load" />
- <arg value="org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem" />
+ <arg value="org.apache.hadoop.fs.s3a.S3AFileStatus" />
</hadoop>
- <echo>checknative</echo>
+ <echo>s3guard: ignore a "42" error</echo>
+ <hadoop failonerror="false">
+ <arg value="s3guard" />
+ </hadoop>
+ <echo>checknative</echo>
<echo>
Checking for native binaries;
check.native.binaries=${check.native.binaries}
</echo>
@@ -1274,6 +1279,7 @@ Message is in file ${message.out}
<arg value="checknative" />
</hadoopq>
+
</target>
<target name="s3a.copy.sdk" depends="mvn-copy-dependencies"
@@ -1365,18 +1371,18 @@ Message is in file ${message.out}
<arg value="-h" />
<arg value="file://${target}" />
</ahadoop>
-
- <echo>s3guard help</echo>
+ <echo>Locating a class in hadoop-azure JAR</echo>
<ahadoop>
- <arg value="s3guard" />
- <arg value="help" />
+ <arg value="${findclass}" />
+ <arg value="load" />
+ <arg value="org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem" />
</ahadoop>
- <echo>findclass azure</echo>
+ <echo>Locating a class in hadoop-aws JAR</echo>
<ahadoop>
<arg value="${findclass}" />
<arg value="load" />
- <arg value="org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem" />
+ <arg value="org.apache.hadoop.fs.s3a.S3AFileStatus" />
</ahadoop>
<echo>checknative</echo>
diff --git a/src/releases/release-info-3.4.3.properties
b/src/releases/release-info-3.4.3.properties
index 14a45df..11a9ff2 100644
--- a/src/releases/release-info-3.4.3.properties
+++ b/src/releases/release-info-3.4.3.properties
@@ -19,15 +19,15 @@ hadoop.version=3.4.3
rc=RC1
previous.version=3.4.2
release.branch=3.4.3
-git.commit.id=c2f160e4889
+git.commit.id=9d50c688466
aws.sdk2.version=2.35.4
# HADOOP-19770 Release Hadoop 3.4.3
jira.id=HADOOP-19770
jira.title=Release Hadoop 3.4.3
-amd.src.dir=https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.4.3-RC0
+amd.src.dir=https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.4.3-RC1
arm.src.dir=${amd.src.dir}
http.source=${amd.src.dir}
-asf.staging.url=https://repository.apache.org/content/repositories/orgapachehadoop-1461
+asf.staging.url=https://repository.apache.org/content/repositories/orgapachehadoop-1465
diff --git a/src/text/vote.txt b/src/text/vote.txt
index 2ee857a..bea9308 100644
--- a/src/text/vote.txt
+++ b/src/text/vote.txt
@@ -28,10 +28,6 @@ Build note: the maven artifacts are off the aarch64 release,
not the x86;
single builds on ec2 VMs through our cloud infra kept resulting in multiple
staging repos,
probably a side effect of our VPN setup.
-A raspberry pi5 is perfectly adequate to cut a release, even with just an SD
Card as the storage.
-I built the x86 release remotely, though as I have an 2016 ubuntu laptop I
could try there too.
-
-
AWS SDK
-------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
