[
https://issues.apache.org/jira/browse/BIGTOP-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026136#comment-14026136
]
Konstantin Boudnik edited comment on BIGTOP-1110 at 6/10/14 5:55 AM:
---------------------------------------------------------------------
Good points Mark! I think we are all in agreement that adding major,
potentially disruptive changes in a middle of a release is a bad idea. However,
bumping say Hive 0.13 to 0.13.1 or Hbase 0.98.2 to 0.98.3 sound pretty harmless
and - considering that 0.8.0 turns out to run longer that anyone wanted - it
might be very sane thing to account for 'dot' bug-fix releases. Are we on the
same page?
WRT RC voting: +1 indeed. I think we'll be able to do much more as our CI infra
is getting rebuilt. Unfortunately, not everyone in the community has handy CI
to experiment with different versions of the stacks
was (Author: cos):
Good points Mark! I think we are all in agreement that adding major,
potentially disruptive changes in a middle of a release is a bad idea. However,
bumping say Hive 0.13 to 0.13.1 or Hbase 0.98.2 to 0.98.3 sound pretty harmless
and - considering that 0.8.0 turns out to run longer that anyone wanted - it
might be very sane thing to account for 'dot' bug-fix releases. Are we on the
same page?
> 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: Konstantin Boudnik
> 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.2#6252)
