Bumping this up. Adding the [DISCUSS] text to make this message stand out of your inbox.
I certainly missed this message and only realized 3.3.5 has more than just security updates. What was the issue with the ARM64 build? I was able to publish ARM64 build for 3.3.1 release without problems. On Tue, Sep 27, 2022 at 9:35 AM Steve Loughran <ste...@cloudera.com.invalid> wrote: > Mukund has just created the new Hadoop release JIRA, > https://issues.apache.org/jira/browse/HADOOP-18470, and is doing the first > build/test before pushing it up. This is off branch-3.3, so it will have > more significant changes than the 3.3.3 and 3.3.4 releases, which were just > CVE/integration fixes. > > The new branch, branch-3.3.5 has its maven/hadoop.version set to > 3.3.5-SNAPSHOT. > > All JIRA issues fixed/blocked for 3.3.9 now reference 3.3.5. The next step > of the release is to actually move those wontfix issues back to being > against 3.3.9 > > There is still a 3.3.9 version; branch-3.3's maven build still refers to > it. Issues found/fixed in branch-3.3 *but not the new branch-3.3.5 branch- > should still refer to this version. Anything targeting the 3.3.5 release > must be committed to the new branch, and have its JIRA version tagged > appropriately. > > All changes to be cherrypicked into 3.3.5, except for those ones related to > the release process itself, MUST be in branch-3.3 first, and SHOULD be in > trunk unless there is some fundamental reason they can't apply there > (reload4j etc). > > Let's try and stabilise this releases, especially bringing up to date all > the JAR dependencies which we can safely update. > > Anyone planning to give talks at ApacheCon about forthcoming features > already in 3.3 SHOULD > > 1. reference Hadoop 3.3.5 as the version > 2. make sure their stuff works. > > Mukund will be at the conf; find him and offer any help you can in getting > this release out. > > I'd like to get that Arm64 build working....does anyone else want to get > involved? > > -steve >
