You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2016/11/21 19:13:59 UTC
[jira] [Updated] (BIGTOP-2282) Define Bigtop 1.2 release BOM
[ https://issues.apache.org/jira/browse/BIGTOP-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik updated BIGTOP-2282:
---------------------------------------
Summary: Define Bigtop 1.2 release BOM (was: Define Bigtop 1.next (1.1.1 or 1.2) release BOM)
> Define Bigtop 1.2 release BOM
> -----------------------------
>
> Key: BIGTOP-2282
> URL: https://issues.apache.org/jira/browse/BIGTOP-2282
> Project: Bigtop
> Issue Type: New Feature
> Components: general
> Affects Versions: 1.1.0
> Reporter: Konstantin Boudnik
> Priority: Blocker
> Fix For: 1.2.0
>
>
> It is this time again to start thinking about what we'd like to put into the next release, once 1.1.0 is out of the doors.
> I know we have discussed this in the past, but I wonder if trying to make a quick consequent release with just some components updates would be make sense? Obvious candidates will be Hadoop 2.7.2, Hive 1.2.2 (might be ready soon), Spark 1.6.1
> Or the community would rather spend more time and deliver upgraded components along with the improvements to our own software as well?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)