vt921102 commented on PR #8693:
URL: https://github.com/apache/hadoop/pull/8693#issuecomment-6437381149
Thanks for merging, @steveloughran — and noted on AssertJ, I will use it on
both
branches from now on rather than keeping the JUnit 4 style in the 3.4
variant.
On the release question, since that is what I now have to plan around: is a
3.4.4 genuinely off the table, or is it unscheduled because nobody has
volunteered to run it? Those are quite different answers for us.
We are exactly the Java 8 consumer you describe — our product cannot move to
Java 11 on a short timeline, which is why this backport mattered.
HADOOP-19973
is now marked Fixed with 3.4.4 in Fix Version/s, so the fix is sitting on
`branch-3.4` waiting for a release that may never be cut.
Three things it would help me to know:
1. Is there any expectation of a 3.4.4 at all, even far out, or should I
treat
`branch-3.4` as effectively end-of-life for releases?
2. If the blocker is release-manager time rather than the dependency
situation,
is that something a contributor could realistically help with? I am happy
to
help test an RC on Windows and JDK 8 — I already have the environment set
up
from validating this PR.
3. Until then, is building from `branch-3.4` ourselves the sanctioned answer
for
Java 8 users, or is the project's advice simply to plan the move to Java
11+
and 3.5.x?
No urgency on a reply given your break — I would just rather plan against the
real answer than assume one.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
