Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mxnet.incubator.apache.org
MIME-Version: 1.0
References: <4B2FF959-0A42-4637-9E78-26067E68A4CC@gmail.com>
In-Reply-To: <4B2FF959-0A42-4637-9E78-26067E68A4CC@gmail.com>
From: Henri Yandell <bayard@apache.org>
Date: Wed, 13 Sep 2017 21:31:39 +0000
Message-ID: <CALGG8z3SRhK6zX8UFqszG-PkQXFbcjP1nrp=bgec3UcuNyeb=g@mail.gmail.com>
Subject: Re: MXNet: Run PR builds on Apache Jenkins only after the commit is reviewed
To: dev@mxnet.incubator.apache.org
Content-Type: multipart/alternative; boundary="001a1143f3004fbafa055918e3da"
archived-at: Wed, 13 Sep 2017 21:31:58 -0000

--001a1143f3004fbafa055918e3da
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Side note:

There is no "we". The below should say something like "I would like to
propose...", or "As part of my work at <Corporation>, I would like to
propose..." if it's coming from a team at your day job and you don't want
to hog all the glory :)

If it truly is "we", then the email should end with the "we" that the email
is from. For example a release announcement from me would say "We are proud
to release" and would end with "Hen, on behalf of the Apache MXNet project"=
.

Hen

On Mon, Sep 11, 2017 at 17:50 Meghna Baijal <meghnabaijal2017@gmail.com>
wrote:

> Hi All,
> We would like to initiate a change in the way the PR builds are being
> triggered. At the moment, every time a Pull Request is created, a build
> gets triggered on Jenkins. Additional builds also get triggered due to
> changes to the same PR.
> Too many PR builds leads to resource starvation and very long queues and
> long build times. Hence we would like to add some checks where a human
> reviewer manually marks it to something like =E2=80=9Cok to build=E2=80=
=9D before a PR
> build is triggered.
>
> Do you think this approach would be helpful and we should move forward
> with it?
>
> Thanks,
> Meghna Baijal
>
>
>
>

--001a1143f3004fbafa055918e3da--