Mailing-List: contact dev-help@yetus.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@yetus.apache.org
MIME-Version: 1.0
In-Reply-To: <AE7FDE56-73CA-40AF-BF38-0CD127A3A2CB@apache.org>
References: <AE7FDE56-73CA-40AF-BF38-0CD127A3A2CB@apache.org>
From: Andrew Bayer <andrew.bayer@gmail.com>
Date: Tue, 29 Mar 2016 09:31:23 -0700
Message-ID: 
 <CAPbPdOY0=99CZe9u3LVHXWSbv4W8Zden3NMZFvBRgRmz_2n3xg@mail.gmail.com>
Subject: Re: [DISCUSS] Branch for YETUS-156
To: dev@yetus.apache.org
Content-Type: multipart/alternative; boundary=001a114a44067fd1e6052f32906c

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

Branch away, I say. Also I rhyme apparently.

A.

On Tue, Mar 29, 2016 at 9:25 AM, Allen Wittenauer <aw@apache.org> wrote:

>
> Hey gang.
>
>         YETUS-156=E2=80=99s purpose is to give Yetus the ability to act a=
s
> daily/nightly/whateverly build driver for CI systems.  This way, Yetus=E2=
=80=99
> reporting could be part of the CI process rather than just digging throug=
h
> mountains of logs looking for errors.  The vast majority of changes are
> purely cosmetic [yay!] but there are quite a few of them to clean up.
>
>
>         Given:
>
>                 * that we don=E2=80=99t have a branch policy (at least, t=
hat I=E2=80=99m
> aware of=E2=80=A6.)
>                 * YETUS-156 is working well enough in my tests for people
> to start playing with it
>                 * YETUS-156 is probably reaching the point where it is
> =E2=80=98too big to review=E2=80=99 (~40k at last rebase)
>
>         I think it might be useful to setup a branch for YETUS-156,
> preferably with a CTRTM (commit then review then merge)-type policy.  Thi=
s
> would give others a chance to play, break it up into a reviewable state,
> give me a chance to fix bugs quickly while still providing protection to
> master if the 0.3.0 train decides to leave before this is ready.
>
>         In the mean time, I=E2=80=99ve changed YETUS-156 to be an umbrell=
a, if
> just for my own sanity.
>
>         Any thoughts?
>
>         Thanks!

--001a114a44067fd1e6052f32906c--