Thanks a lot for the help to move this release forward.
Some status update:
branch-3.3.6 just forked out of branch-3.3.
Starting a RC0 now.
I would like to add the text to highlight big features and improvements.
Let me know if you have something that's included in this release and would
also li
Thanks for comments
Looking at jiras fixed in 3.3.6 and 3.3.9 (my bad, forgot that most commits
landing in branch-3.3 was 3.3.9), most are okay. We have about 119 commits
so it's manageable.
I am planning to cut 3.3.6 out of branch-3.3 later today. Anything open
that is still targeting 3.3.6 will
That openssl change ain't a blocker now from my side, that ABFS-Jdk-17
stuff got sorted out, Steve knew a way out
On Sat, 6 May 2023 at 00:51, Ayush Saxena wrote:
>
> Thanx Wei-Chiu for the initiative, Good to have quick releases :)
>
> With my Hive developer hat on, I would like to bring som
Thanx Wei-Chiu for the initiative, Good to have quick releases :)
With my Hive developer hat on, I would like to bring some stuff up for
consideration(feel free to say no, if it is beyond scope or feels even
a bit unsafe, don't want to mess up the release)
* HADOOP-18662: ListFiles with recursive
Wei-Chiu has suggested a minimal "things in 3.3.5 which were very broken,
api change for ozone and any critical jar updates"
so much lower risk/easier to qualify and ship.
I need to get https://issues.apache.org/jira/browse/HADOOP-18724 in here;
maybe look at a refresh of the "classic" jars (slf4
Thanks Wei-Chiu for driving this release.
Cherry-pick YARN-11482 to branch-3.3 and mark 3.3.6 as the fixed version.
so far only 8 jiras were resolved in the branch-3.3 line.
If we should consider both 3.3.6 and 3.3.9 (which is from release-3.3.5
discuss)[1] for this release line?
I try to query
