update
1. branch 3.3 has a version of 3.3.9-SNAPSHOT 2. and 3.3.9 should be the version for fixes against this, with 3.3.4 for the new point release 3. please don't use 3.3.4 for branch-3.3 changes from now on I've already got a PR up with the changes; going to create an asf branch-3.3.4 branch mirroring it and kicking off with the pom update. I'm going to do a dry run of a release this week to build the binaries on x86 and ARM but not put for a vote as I am away next week. instead it'll be a validation of my processes, ant-based automation etc. ( https://github.com/steveloughran/validate-hadoop-client-artifacts) I will kick off the release the following week, which, being july4 week, may have more people offline. it does give larry a chance to get https://issues.apache.org/jira/browse/HADOOP-18074 in, as it may have security implications. On Mon, 20 Jun 2022 at 19:02, Steve Loughran <ste...@cloudera.com> wrote: > I'm setting things up for a new release > > https://issues.apache.org/jira/browse/HADOOP-18305 > > absolute minimum of fixes. as well as some related to ZK lockdown, i would > like to include > > https://issues.apache.org/jira/browse/HADOOP-18303 > remove shading exclusion of javax.ws.rs-api from hadoop-client-runtime > > and > https://issues.apache.org/jira/browse/HADOOP-18307 > remove hadoop-cos as a dependency of hadoop-cloud-storage > > the last one is a lstminute workaround for, a classpath ordering issue due > to too many libraries having unshaded references to mozilla/prefix-list.txt > https://issues.apache.org/jira/browse/HADOOP-18159 > > the proper fixes would be getting that updated library tested (who is set > up to test tencent cloud?) and ideally (aws, cos, gcs shaded libraries to > shade their references) > > for 3.3.4, i am just going to cut the declaration of the module as a > dependency of hadoop-cloud-storage so out of downstream apps unless they > explicitly ask forit. > > now, numbering > > > 1. I am calling this 3.3.4 > 2. I am going to increase the version of branch 3.3. to 3.3.9. that > leaves space for some more but doesn't confuse jira dropdown dialogs. > > > i do believe branch-3.3. should be renamed branch-3.4 and the release i > plan to do with mukund called 3.4.0, but that is another bit of project > organisation. > > expect the first RC up soon, I am going to be away on vacation from june > 28 to july 23 though, which complicates things > > >
