Re: [DISCUSS] Release Hadoop 3.4.0

2024-01-12 Thread slfan1989
:08:36 Subject: Re: Re: [DISCUSS] Release Hadoop 3.4.0 To: , , < ste...@cloudera.com> Cc: , Ayush Saxena , < hexiaoq...@apache.org> Thank you for reporting this issue and helping resolve it! I will try to release hadoop-thirdparty 1.2.0-RC0 version first. Best Regards, Shilun Fa

Re: Re: [DISCUSS] Release Hadoop 3.4.0

2024-01-05 Thread Ayush Saxena
Thanx @slfan1989 for volunteering. Please remove this [1] from the new branches-3.4 & 3.4.0 when you create them as part of preparing for the release, else it would be putting up trunk labels for backport PRs to those branches as well. There are some tickets marked as Critical/Blocker for 3.4.0

Re: Re: [DISCUSS] Release Hadoop 3.4.0

2024-01-04 Thread slfan1989
Hey all, I plan to create a new branch of branch-3.4.0 this weekend and change the version of the trunk branch to 3.5.0-SNAPSHOT. If all goes well, I will release hadoop-3.4.0-RC0 early next week. hadoop-3.4.0 contains many changes, we may release multiple RC versions. Best Regards, Shilun

Re: Re: [DISCUSS] Release Hadoop 3.4.0

2024-01-04 Thread slfan1989
Hey all, We are planning to release Hadoop 3.4.0 base on trunk. I made some preparations and changed the target version of JIRA for non-blockers in HADOOP, HDFS, YARN, and MAPREDUCE from 3.4.0 to 3.5.0. If we want to create a new JIRA, the target version can directly select version 3.5.0. If you

Re: [DISCUSS] Release Hadoop 3.4.0

2024-01-03 Thread Mukund Madhav Thakur
+1 from me. It will include the new AWS V2 SDK upgrade as well. On Wed, Jan 3, 2024 at 6:35 AM Xiaoqiao He wrote: > > > > I think the release discussion can be in public ML? > > Good idea. cc common-dev/hdfs-dev/yarn-dev/mapreduce-dev ML. > > Best Regards, > - He Xiaoqiao > > On Tue, Jan 2,

Re: [DISCUSS] Release Hadoop 3.4.0

2024-01-03 Thread Xiaoqiao He
> > I think the release discussion can be in public ML? Good idea. cc common-dev/hdfs-dev/yarn-dev/mapreduce-dev ML. Best Regards, - He Xiaoqiao On Tue, Jan 2, 2024 at 6:18 AM Ayush Saxena wrote: > +1 from me as well. > > We should definitely attempt to upgrade the thirdparty version for >