Thanks all for your feedback, I will start an official vote thread.
Best Regards,
- He Xiaoqiao
On Tue, Dec 5, 2023 at 11:23 PM Masatake Iwasaki
wrote:
> +1 on marking 3.2 EOL.
>
> For branch-2.10, just keeping cherry-picking critical our CVEs without
> release sounds good.
> If someone really
+1 on marking 3.2 EOL.
+1 just keeping cherry-picking critical our CVEs without release on
branch-2.10.
+1 The new version is released based on version 3.4.0.
I am willing to take on the work during the release of the new version and
look forward to a smooth release.
Best Regards,
Shilun Fan.
+1 on marking 3.2 EOL.
For branch-2.10, just keeping cherry-picking critical our CVEs without
release sounds good.
If someone really want, I can try to put 2.10.3 up.
dev-support/bin/create-release looks still working with some trivial fixes.
On Tue, Dec 5, 2023 at 7:45 PM Steve Loughran
wrote:
+1 for making 3.3 and 3.4 the maintained lines
3.2.x we should say -as it is true- that the age of the dependencies is
such that it is transitively insecure. To fix those, people must upgrade.
For 2.10.x, we should think about whether to cherrypick our own CVEs there,
but not actually do any new
Thanks Ayush for your corrections. It is actually 2023 about release-3.3.5.
On Tue, Dec 5, 2023 at 4:54 AM Ayush Saxena wrote:
> Thanx He Xiaoqiao for starting the thread.
>
> +1 to mark 3.2 EOL. I am not sure about branch-2 stuff, I think a
> bunch of folks are still using Hadoop 2.x, but we ha
Thanx He Xiaoqiao for starting the thread.
+1 to mark 3.2 EOL. I am not sure about branch-2 stuff, I think a
bunch of folks are still using Hadoop 2.x, but we hardly push anything
over there & I am not sure if anyone is interested in releasing that
or not.
> Hadoop 3.3 Release (release-3.3.5 at J
