Mailing-List: contact dev-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.incubator.apache.org
Received-SPF: error (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Build notifications spamin the dev list
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
In-Reply-To: 
 <CAGU5spcvczOtBx2S2oynRkEn34HS-rFGFtkEb5Q-N-NXx7rUrA@mail.gmail.com>
Date: Sat, 22 Jun 2013 09:36:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D3F1AAB-9E20-4738-9CDC-29F496195A08@jordanzimmerman.com>
References: 
 <CAGU5spcvczOtBx2S2oynRkEn34HS-rFGFtkEb5Q-N-NXx7rUrA@mail.gmail.com>
To: dev@curator.incubator.apache.org

I've been fixing them. I fixed a major one having to do with git tags =
(Apache/Jenkins issue). And I'm working on the other ones.

-JZ

On Jun 21, 2013, at 8:48 PM, Luciano Resende <luckbr1975@gmail.com> =
wrote:

> When I open my curator dev list folder, most all the things I see is =
failed
> build notifications. I think that this is usually bad for someone that =
is
> coming fresh to the community, where the first impression will be that
> there is nothing much going on other then broken code.
>=20
> Could we look into other ways we could handle this ? Fixing the build =
would
> be the best, but maybe reducing the frequency of the builds or just =
sending
> e-mails to whoever broke the build (and then only have a daily build =
that
> goes to the dev list) ?
>=20
> Thanks
>=20
> --=20
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/