Looking at the EOL policy wiki:
https://cwiki.apache.org/confluence/display/HADOOP/EOL+%28End-of-life%29+Release+Branches
The Hadoop community can still elect to make security update for EOL'ed
releases.
I think the EOL is to give more clarity to downstream applications (such as
HBase) the guidan
Hi Wei-Chiu
Extremely sorry for the late reply here.
Cud u pls help to add more clarity on defining what will happen for
branch-2.8 when we call EOL.
Does this mean that, no more release coming out from this branch, or some
more additional guidelines?
- Sunil
On Mon, Feb 24, 2020 at 11:47 PM We
This thread has been running for 7 days and no -1.
Don't think we've established a formal EOL process, but to publicize the
EOL, I am going to file a jira, update the wiki and post the announcement
to general@ and user@
On Wed, Feb 19, 2020 at 1:40 PM Dinesh Chitlangia
wrote:
> Thanks Wei-Chiu
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1420/
[Feb 23, 2020 8:55:39 AM] (ayushsaxena) HDFS-15041. Make MAX_LOCK_HOLD_MS and
full queue size configurable.
[Feb 23, 2020 6:37:18 PM] (ayushsaxena) HDFS-15176. Enable GcTimePercentage
Metric in NameNode's
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/606/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc c
