I have done the change.
All committers,
2.8.2 release is supposed to be a stable/production release for
branch-2.8. For commits to go for 2.8.2 release (only important and low risk
bug fixes), please commit to trunk, branch-2, branch-2.8 and branch-2.8.2. For
unimportant or high risk
Folks,
With the release for 2.8, we would like to look ahead to 2.9 release as
there are many features/improvements in branch-2 (about 1062 commits), that
are in need of a release vechile.
Here's our first cut of the proposal from the YARN side:
1. Scheduler improvements (decoupling
Nice catch, Brahma. Actually, this is not supposed to be happen as we all
should know the patch should firstly get landed on branch-2.8 (as well as
trunk, branch-2) before landed on branch-2.8.2. Anyway, we will always check
JIRAs claim to fixed in a specific release version with commits
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/474/
[Jul 24, 2017 6:09:03 AM] (sunilg) YARN-6102. RMActiveService context to be
updated with new RMContext on
-1 overall
The following subsystems voted -1:
findbugs unit
The following subsystems
