Jenkins build is back to normal : Bigtop-trunk-testartifacts #1011

See

Re: [DISCUSS] Setting up long term support mindset

A lot of behavior among loosely coupled projects is emergent. So in that sense some of what bigtop can produce is defined by something beyond direct control. What you can do is try to influence the processes at work. So, outreach to each component project. Also, constructive pressure. Publicize big

Q, Integration Classic Hama with current bigtop trunk

Hi gurus, Currently TRUNK is based on Hadoop 2.0, right? We (Hama team) are think about addressing HDFS 2.0 compatibility issue first to support 'classic Hama cluster mode' on top of existing Hadoop 2.0 cluster, before YARN integration. My question is - once compatibility issue has been solved, ca

Re: [DISCUSS] Setting up long term support mindset

On Wed, Mar 6, 2013 at 10:10 AM, Konstantin Boudnik wrote: > I believe there's not much more to say about it, except that this is, > in my opinion, a good way to establish our project as de-facto go-to > place for community driven Hadoop based stacks and a focal point for > the integration in the

[DISCUSS] Setting up long term support mindset

I want to throw in the following discussion topic. We are clearly having integration issues when putting together bleeding edge Hadoop based stacks. I don't want to argue about the roots of the phenomena not about how it can be fixed. The purpose of this discussion is different. There is an ongo

Re: [DISCUSS] stabilizing Hadoop releases wrt. downstream

On Wed, Mar 06, 2013 at 07:24AM, Arun C Murthy wrote: > Cos, > > On Mar 4, 2013, at 10:15 PM, Konstantin Boudnik wrote: > > > The issue that a downstream > > integration project is likely to have is - for once - the absence of > > regularly published development artifacts. In the light of "it did

Jenkins build is still unstable: Bigtop-trunk-iTest » iTest: system and integration testing in the cloud #965

See

Jenkins build is unstable: Bigtop-trunk-iTest #965

See

Re: [DISCUSS] stabilizing Hadoop releases wrt. downstream

Cos, On Mar 4, 2013, at 10:15 PM, Konstantin Boudnik wrote: > The issue that a downstream > integration project is likely to have is - for once - the absence of > regularly published development artifacts. In the light of "it didn't > happen if there's no picture" here's a couple of examples: M