[
https://issues.apache.org/jira/browse/BIGTOP-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883119#comment-13883119
]
Andrew Purtell commented on BIGTOP-1110:
----------------------------------------
bq. What do you guys think about Hadoop 2.3 then? Any feedback?
My above concern was about a looming API discontinuity, but that has been
resolved in favor of not breaking a downstream project midway in the 2.x
release series.
If 2.3.0 is released with sufficient lead time for 0.8, I think we should
consider it. Or 2.4.0 for that matter. We generally take the most recent
releases of the stack as informal policy, to try to increase usage and test
coverage of these things? Other policies are reasonable also, if I am mistaken
or if we want to do things differently.
Looking at the Fix Version report for 2.3.0:
https://issues.apache.org/jira/issues/?jql=project%20in%20(HADOOP%2C%20HDFS%2C%20HDT%2C%20MAPREDUCE%2C%20YARN)%20AND%20fixVersion%20%3D%20%222.3.0%22%20ORDER%20BY%20key%20ASC
, from a distribution perspective:
HADOOP-9623 is a dependency version change but I can't seem to get the S3 or
S3N filesystems working without it.
HADOOP-10110 moves jetty-util to test scope, that's probably fine.
HADOOP-10255 isn't resolved yet but is the cure for the above mentioned API
discontinuity.
Looks like many NFS gateway fixes and doc updates landed here.
There are several issues with the UIs that will be fixed.
Looks promising, caveat enough time for testing.
> Define BOM for 0.8.0 release of Bigtop
> --------------------------------------
>
> Key: BIGTOP-1110
> URL: https://issues.apache.org/jira/browse/BIGTOP-1110
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.7.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.8.0
>
>
> This JIRA is going to be a rolling list of our thinking on what BOM makes
> sense for Bigtop 0.8.0 singularity release.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
