Hi Olaf. Thanks, i will merge back to master and update the instructions as well. I have some changes on brancg-1.1 which need to be merged anyway, so it is easy.
Cheers On January 28, 2016 6:28:08 AM PST, Olaf Flebbe <[email protected]> wrote: >Hi Cos, > >I commited BIGTOP-2281 only to branch-1.1.How should I contribute this >to master ? >The instructions we have in Confluence do not apply to this situation. > >Olaf > > > >> Am 28.01.2016 um 00:57 schrieb Konstantin Boudnik <[email protected]>: >> >> I have forked branch-1.1 and bumped version on master to >1.2.0-SNAPSHOT >> There's still a couple of tickets left against 1.1 for power8 and >hive, but I >> hope will get them resolved today/tomorrow. >> >> For committers who will be committing these patches: PLEASE, PRETTY >PLEASE - >> do commit them into branch-1.1 and we will merge it back to master, >as were >> discussed before. If you bring the commits to master first - we'll >have commit >> hash-sums discrepancies again and it will be ugly. >> >> Thank you very much! >> Cos >> >> On Thu, Nov 26, 2015 at 11:21AM, Konstantin Boudnik wrote: >>> From the CI standpoint we are in the good shape for the release. Two >issues >>> left are >>> - xmlto packaging is still missing in the suse container, causing >sqoop to fail >>> - incorrect %if in the spec of tez RPM, causing it to fail on suse >>> >>> The rest seems to be fix, at least from the build standpoint. There >are still >>> issues like BIGTOP-2154, but at least it doesn't affect build. It >still has to >>> be fixed of course. >>> >>> Hopefully Mahout 0.11.1 is ready to be included in the next a couple >of days, >>> and other than that I can no think of anything else blocking us. >>> Last call for release manager volunteers...? >>> >>> If not, I would be happy to cut branch-1.1 and prep RC1 for the next >release >>> soon. >>> >>> Cos >>> >>> On Wed, Nov 11, 2015 at 01:36AM, Evans Ye wrote: >>>> Overall I'm happy to see 1.1 release at the end of November. >>>> We might get some benefits by providing the newest stack one step >ahead the >>>> other hadoop vendors. >>>> My resource is very tight recently. However, I can provide help on >the ci >>>> side if needed. :) >>>> >>>> 2015-11-08 2:40 GMT+08:00 Konstantin Boudnik <[email protected]>: >>>> >>>>> On Sat, Nov 07, 2015 at 01:21PM, Suneel Marthi wrote: >>>>>> FYI, we had a Mahout 0.11.1 release last night, this adds Spark >1.4+ >>>>>> compatibility to Mahout and also includes other Samsara >Performance >>>>>> improvements. >>>>> >>>>> Cool! Do you mind creating a JIRA in Bigtop for the version bump? >Please >>>>> link >>>>> it to BIGTOP-2078 as well. Thanks! >>>>> >>>>>> On Sat, Nov 7, 2015 at 1:17 PM, Andrew Purtell ><[email protected] >>>>>> >>>>>> wrote: >>>>>> >>>>>>> I'm aiming to get the HBase release 0.98.16 out the door next >week and >>>>>>> will post a patch to update the BOM for 1.1 after. >>>>>>> >>>>>>>> On Nov 7, 2015, at 10:03 AM, Konstantin Boudnik ><[email protected]> >>>>> wrote: >>>>>>>> >>>>>>>> Thank you very much Yeongeon - looking forward for your >contribution! >>>>>>>> >>>>>>>> Cos >>>>>>>> >>>>>>>>> On Sat, Nov 07, 2015 at 11:00PM, YEONGEON wrote: >>>>>>>>> Thank for your mention. >>>>>>>>> I reviewed the issue( >>>>> https://issues.apache.org/jira/browse/BIGTOP-2078) >>>>>>> in >>>>>>>>> detail again and understood what it means. >>>>>>>>> I also think it would be better to add the Tajo at the Bigtop >1.2 >>>>>>> after. I >>>>>>>>> will try to build more carefully to go well with the Bigtop. >>>>>>>>> >>>>>>>>> Yeongeon >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 2015-11-07 10:49 GMT+09:00 Konstantin Boudnik ><[email protected]>: >>>>>>>>> >>>>>>>>>> I'd say if it is integrated into the stack before the release >>>>> branch is >>>>>>>>>> cut-off it'd be great to have it. Otherwise there's going to >be 1.2 >>>>>>> shortly >>>>>>>>>> after. >>>>>>>>>> >>>>>>>>>> Cos >>>>>>>>>> >>>>>>>>>>> On Sat, Nov 07, 2015 at 10:23AM, YEONGEON wrote: >>>>>>>>>>> I'm going to add Tajo 0.11.0 ( >>>>>>>>>>> https://issues.apache.org/jira/browse/BIGTOP-1641) on >Bigtop. >>>>>>>>>>> If it would be possible, I could try pull-request until end >of >>>>> Nov. >>>>>>>>>>> >>>>>>>>>>> 2015-11-07 6:28 GMT+09:00 Grimes Michael <[email protected]>: >>>>>>>>>>> >>>>>>>>>>>> It¹d be nice to get Oozie 4.2.0 in as well >>>>>>>>>>>> (https://issues.apache.org/jira/browse/BIGTOP-1915). 4.0.1 >is >>>>> over >>>>>>> two >>>>>>>>>>>> years old. I¹ll be uploading a patch for it here pretty >soon. >>>>>>>>>>>> >>>>>>>>>>>>> On 11/6/15, 12:53 PM, "Olaf Flebbe" <[email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Just included the long overdue hue-3.9 update. >>>>>>>>>>>>> >>>>>>>>>>>>> I have a couple of puppet code changes I like to commit. >>>>>>>>>>>>> >>>>>>>>>>>>> Olaf >>>>>>>>>>>>> >>>>>>>>>>>>>> Am 06.11.2015 um 21:23 schrieb Konstantin Boudnik < >>>>> [email protected] >>>>>>>> : >>>>>>>>>>>>>> >>>>>>>>>>>>>> Guys, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I have put a draft of 1.1 BOM to >>>>>>>>>>>>>> https://issues.apache.org/jira/browse/BIGTOP-2078 >>>>>>>>>>>>>> Thinking of making the release before the end of >November. >>>>> What's >>>>>>>>>> the >>>>>>>>>>>>>> community take on this? And if there anyone who wants to >do >>>>> the RM >>>>>>>>>> this >>>>>>>>>>>>>> time >>>>>>>>>>>>>> around? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Looks like we are mostly ok. excluding >>>>>>>>>>>>>> Phoenix (BIGTOP-1942) >>>>>>>>>>>>>> Zeppeling (BIGTOP-1769) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Could perhaps component maintainers to take a look at >these >>>>> two?A >>>>>>>>>>>>>> >>>>>>>>>>>>>> Anything else we should be including? Thanks >>>>>>>>>>>>>> Cos >>>>>>>>>> >>>>>>> >>>>> >> >>
