asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hillery <>
Subject Re: [IMPORTANT] Git issues
Date Wed, 15 Jul 2015 09:15:27 GMT
Yes, that's also a possibility, although it wouldn't be my first choice,
for what that's worth. The Github PR interface is pretty minimal, in my
experience. Gerrit is noisy and obtuse but it is pretty powerful. Also, we
do make use of Gerrit's integration with Jenkins for launching test runs on
code reviews. Certainly that could all be rewritten to work with Github PRs
(or Review Board, or...), but that seems like a pretty high price to pay if
we don't need to.

aka Chris Hillery

On Wed, Jul 15, 2015 at 2:02 AM, Jochen Wiedmann <>

> Hi, Chris,
> sorry for chiming in (I seem to be doing that a lot, lately.)
> On Wed, Jul 15, 2015 at 10:33 AM, Chris Hillery <>
> wrote:
> > process, set their upstream "origin" remote be set to the read-only
> Github
> > mirror.
> I agree with you, Chris, that the Gerrit discussion is orthogonal.
> (That discussion was mainly triggered by me in order to find a
> resolution, which might be acceptable for both the Incubator as the
> overseeing entity, and for the project members of AsterixDB.
> Using the github mirror as a remote "origin" might lead to another
> possible reolution. The Github mirrors are officially endorsed, thus
> accepted by the Incubator. So, if AsterixDB could replace Gerrit with
> Github PRs, we'd essentially have the same situation in terms of
> process (but with slightly less comfort, and a different UI). I can
> even imagine, that, in the foreseeable future, there will be an
> automated way back from the Github Mirror to the ASF repository, given
> how active users are on the Github mirrors by creating PRs.
> Jochen
> --
> Any world that can produce the Taj Mahal, William Shakespeare,
> and Stripe toothpaste can't be all bad. (C.R. MacNamara, One Two Three)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message