[
https://issues.apache.org/jira/browse/BIGTOP-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882207#comment-13882207
]
Roman Shaposhnik commented on BIGTOP-1110:
------------------------------------------
[~mgrover] Crunch 0.9 makes a lot of sense -- I'll update the list. As for
RHEL5 support -- if there's something I might fight for on that proposal it is
dropping support for it. So unless there's anybody with a *really* strong use
cases for it -- I suggest we drop it.
[~cos] [~apurtell] What do you guys think about Hadoop 2.3 then? Any feedback?
[~bmahe] Since Bigtop 0.8.0 will be late April/early May we can simply go with
the latest LTS at that point (14.04) unless of course, there's a strong
objection.
[~cos] [~apurtell] [~bmahe] As for the JDK6 support, let me ask you this guys:
even if we keep it for the Bigtop 0.8.0 BOM, what would
be your criteria for dropping it completely? Also, would it make sense if we
commit to keeping it as a build environment in Bigtop 0.8.0 but fully migrate
to [Open]JDK7 as far as deployment is concerned? Thoughts?
> 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)
