Mailing-List: contact user-help@bigtop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bigtop.apache.org
Received-SPF: pass (nike.apache.org: domain of jayunit100.apache@gmail.com
 designates 209.85.216.174 as permitted sender)
From: Jay Vyas <jayunit100.apache@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Gearing up for 0.9
Message-Id: <13DB8D76-7572-400A-9CC3-EC7268308534@gmail.com>
Date: Fri, 6 Mar 2015 14:25:54 -0500
References: <20150228185619.GB4732@boudnik.org>
 <20150306192326.GR1657@boudnik.org>
In-Reply-To: <20150306192326.GR1657@boudnik.org>
To: "user@bigtop.apache.org" <user@bigtop.apache.org>

Iirc we don't have any maintainers for it. =20
Is anyone interested in maintaining it?

> On Mar 6, 2015, at 2:23 PM, Konstantin Boudnik <cos@apache.org> wrote:
>=20
> Does anyone know what's the story with Mahout? Has it been fixed to be wor=
king
> with Hadoop2 or shall we remove it from the BOM?
>=20
> Cos
>=20
>> On Sat, Feb 28, 2015 at 06:56PM, Konstantin Boudnik wrote:
>> Guys,
>>=20
>> It'd be great if we can have the next release ready by ApacheCon in April=
.
>> Think about all the PR and publicity we can get without any effort on our=
 own.
>> And perhaps from the tactical standpoint we shall call this release 1.0?
>>=20
>> I believe the only major hurdle between us and the release is CI. Roman, I=

>> understand you're busy elsewhere, but could you please let us know what e=
lse
>> needs to be done before we can start doing the regular builds and how the=

>> community can help. That's the highest priority, IMO.
>>=20
>> There a couple of the tickets left unfixed/unassigned on BIGTOP-1480, and=
 if
>> they aren't resolved on time we can move them farther. There's lesser tha=
n a
>> half-dozen blockers and none of them look too big, honestly. And we have a=

>> whole lot of active committers and contributors to wrap-up the release in=
 a
>> couple of weeks.
>>=20
>> Do we want to try upgrade to HBase 1.x for this release or it might be to=
o big
>> of a distortion? Andrew, what do you think and do you have cycles to do t=
hat?
>>=20
>> What else we need to get done for this release? Suggestions?
>>=20
>> Is there anyone who wants to step up as the RM this time around? RM doesn=
't
>> mean that you have to do all the job, but rather be an efficient with a s=
tick ;)
>>=20
>> Thoughts?
>>  Cos