I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2804/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 32910 lines...]
Running
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/866/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9752 lines...]
Running
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/867/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9692 lines...]
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2805/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 32913 lines...]
Tests run: 1, Failures: 0, Errors:
Kai Sasaki created MAPREDUCE-6601:
-
Summary: Fix typo in Job#setUseNewAPI
Key: MAPREDUCE-6601
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6601
Project: Hadoop Map/Reduce
Issue Type:
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2806/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 33014 lines...]
Tests run: 1, Failures: 0, Errors:
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2803/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 33377 lines...]
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/864/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 10819 lines...]
Running
The general rule sounds good to me.
> "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
get out after 2.x.y release date"
+1
> I would prefer this rule only applies on critical/blocker fixes, but
not applies on minor/trivial issues.
+1
Thanks,
Akira
On 12/29/15
10 matches
Mail list logo
