Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
References: 
 <CA+ULb+tm9r6DYmeRbtAkM_z68T7gJTAMqzVmsOmSQAx6rC3q+Q@mail.gmail.com>
 <CAPgpW0bOfrb5Yk_Ne9O45xRBY+V9813oqRUYDxN_nx2mJpC3HQ@mail.gmail.com>
 <CAPgpW0bKAmEa=ZycvySm9cp5nes_eFh3f34ov-CgKuDNg8u8WQ@mail.gmail.com>
 <CAH=zMbqKitBGg4QS1wzq6kE3qQo831jFDxaGFCLTV6MCGUSUAg@mail.gmail.com>
 <CAPgpW0aexxZbBh5HsbRk30o7iUkh=2G4k9YMi5ZKp8c-6LyfdA@mail.gmail.com>
 <CA+ULb+vQw=ODzCPFtNiZhmPK3_HWw-tLV+BFS3fbkQ__1ON0Tw@mail.gmail.com>
 <CAG+aQF=uJyLPqEy1r-1igrMQjszj8vvAtnc_NdGestYecj=FeQ@mail.gmail.com>
In-Reply-To: 
 <CAG+aQF=uJyLPqEy1r-1igrMQjszj8vvAtnc_NdGestYecj=FeQ@mail.gmail.com>
From: "Ting(Goden) Yao" <tyao@pivotal.io>
Date: Mon, 11 Jan 2016 21:18:31 +0000
Message-ID: 
 <CAPgpW0av8Wza=Kaq7gMsdp_5mUHoQZ5TZAAQEc0GuzCx-ip9Uw@mail.gmail.com>
Subject: Re: What's blocking our formal release candidate
To: Noa Horn <nhorn@pivotal.io>, dev <dev@hawq.incubator.apache.org>
Content-Type: multipart/alternative; boundary=089e011827d62bb5480529157b66

--089e011827d62bb5480529157b66
Content-Type: text/plain; charset=UTF-8

I can see a few areas we can improve in terms of the commit process.
We have a community guideline for commit process on wiki:
https://cwiki.apache.org/confluence/display/HAWQ/Contributing+to+HAWQ#ContributingtoHAWQ-Commitprocess(forcommitters
)

Original Commit :
1> missing a JIRA#
2> probably didn't strictly follow the guideline above. We should be able
to catch build breaking issues before we actually commit.

Revert Commit:
1> also missing a JIRA#
2> probably need to communicate in the dev mailing list for visibility of
the community and get consensus.

Other issue:
1> Jenkins reported SUCCESS on a broken build.

As these are more general process discussion, let's spin off a separate
thread for discussion. (I'll start shortly)

*Back to this thread, we need unblock our formal release.*
Roman, can you help fix the original commit C comment issue and re-submit,
Please use https://issues.apache.org/jira/browse/HAWQ-184 (pass RAT check) or
create sub-task if you want to be more specific.

-Goden

On Mon, Jan 11, 2016 at 11:59 AM Noa Horn <nhorn@pivotal.io> wrote:

> As far as I know, it was mentioned in the PR itself that the build is
> broken. No fix was pushed for about a week. According to the guidelines of
> the committing process, a commit that breaks the build should be reverted
> within 24 hours.
>
> If you look at the build output for this PR (
> https://github.com/apache/incubator-hawq/pull/243), you can see it is
> broken
> https://builds.apache.org/job/HAWQ-build-pullrequest/83/console.
> Unfortunately, the build return value is SUCCESS despite compilation errors.
>
> Thanks,
> Noa
>
>
>
> On Mon, Jan 11, 2016 at 10:53 AM, Roman Shaposhnik <roman@shaposhnik.org>
> wrote:
>
>> On Mon, Jan 11, 2016 at 10:27 AM, Ting(Goden) Yao <tyao@pivotal.io>
>> wrote:
>> > Hi , I see the previous Roman's commit
>> > (https://github.com/apache/incubator-hawq/pull/243 ) was reverted by
>> >
>> https://github.com/apache/incubator-hawq/commit/e48a07b0d8a5c8d41d2d4aaaa70254867b11ee11
>>
>> I actually would like to understand why it got reverted. Was there a build
>> that got broken by it (ok, I think I know the reason -- but the fact that
>> it got reverted silently bothers me and I'd like to understand the overall
>> reasoning when something like this happens).
>>
>> > Can we fix the C comment issue and re-submit the commit. this is
>> blocking
>> > final Apache Release.
>> > Please use: https://issues.apache.org/jira/browse/HAWQ-184 (pass RAT
>> check)
>> > for the future commits regarding the clean up and license issue.
>>
>> First of all, it would be great to understand what is the  public
>> criteria for
>> a commit like that to persist in the code base. Is there a public CI that
>> I can leverage to understand whether I'm on the right track or not?
>>
>> Thanks,
>> Roman.
>>
>
>

--089e011827d62bb5480529157b66--