Thanks Ahmar for starting this thread.
Strong +1 to have 3.4.0 from trunk rather than from 3.3.*. We
should keep release line clear, and it's not standard operation
to cut a branch from another line.
Let's move the trunk to 3.5.0-SNAPSHOT when we come to an
agreement at this thread. About this rel
gmail.com >;
Date:2023/12/1 22:28
To:"Ahmar Suhail"< ah...@apache.org >;
CC:"common-dev"< common-...@hadoop.apache.org >;"hdfs-dev"<
hdfs-dev@hadoop.apache.org >;"yarn-dev"< yarn-...@hadoop.apache.org >;
"mapreduce-dev&quo
Hi Ahmar,
Makes sense to have a 3.4.0 rather than a 3.3.x if there are major
changes. Few things on the process:
* trunk should now point to 3.5.0-SNAPSHOT
* Fix Versions of all the tickets merged to trunk would be 3.4.0 as of
now, you need to move it to 3.5.0, else while chasing the release, the
Hey all,
HADOOP-18073 was recently merged to trunk, which upgrades the AWS SDK to
V2. Since this merge, there has been work for stabilising this SDK version
upgrade, as tracked in HADOOP-18886. Further, HADOOP-18995 and HADOOP-18996
added support for Amazon Express One Zone.
The SDK upgrade has
