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 release notes will get messed up. * Since we are moving to 3.4.x, we can even explore a few more changes in trunk as well, which weren't merged to 3.3.x due to compat issues. HADOOP-13386 is one such change, which was asked for some time back. * Now we have an additional release line, we can start a thread and think about marking some existing release lines as EOL, so, the number of active release lines stay in control, maybe 3.2 Rest, Good Luck, Thanx for volunteering!!! -Ayush On Fri, 1 Dec 2023 at 17:30, Ahmar Suhail <ah...@apache.org> wrote: > > 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 brought major code changes to the hadoop-aws module. > For example, In the v2 SDK, all package, class and method names have > changed. Due to the upgrade being a large change, it might be good to > release these changes as Hadoop 3.4.0. For this, I started creating a > branch-3.4 from branch-3.3 and branch-3.4.0 for a possible release early > next year. > > > The other option would be to release from trunk as a 3.3.x release, but due > to the large number of changes there this will be really difficult. > > > Thoughts on a 3.4.0 release? --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
