Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Subject: Re: [VOTE] Release of Apache Falcon 0.10 RC0
MIME-Version: 1.0
From: Ying Zheng <yzheng@hortonworks.com>
To: "dev@falcon.apache.org" <dev@falcon.apache.org>, Peeyush Bishnoi
	<bpeeyush@yahoo.co.in>
Thread-Topic: [VOTE] Release of Apache Falcon 0.10 RC0
Thread-Index: AQHR5tCe6kMFtMh/bE+nICtndgouDKAp1rCAgAEqFoCAAR+0gP//q9UA
Date: Wed, 27 Jul 2016 06:06:12 +0000
Message-ID: <D3BD9D41.11922%yzheng@hortonworks.com>
References: <D3BBF600.42212%bvellanki@hortonworks.com>
 <B48E91D7-1B28-425E-A081-C4CE9D5A4A71@hortonworks.com>
 <CAByV4usxG=rFq9icDO4MWe9WqxXM3DhRf1MORuH6zc3r9kPrOw@mail.gmail.com>
 <221696482.6608886.1469592445905.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <221696482.6608886.1469592445905.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [67.161.13.186]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <46911870A8684440BA756719E397243C@exch080.serverpod.net>
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 27 Jul 2016 06:06:29 -0000

I=B9m able to build successfully on my laptop too. No UT and IT test failur=
e.

Thanks,
Ying


On 7/26/16, 9:07 PM, "Peeyush Bishnoi" <bpeeyush@yahoo.co.in.INVALID>
wrote:

>Praveen,
>I am able to build Falcon from source without any issue.
>The respective IT ExtensionManagerIT has not failed for me and build is
>successful.
>Thanks,---Peeyush=20
>
>    On Tuesday, 26 July 2016 4:27 PM, Praveen Adlakha
><praveen.adlakha@inmobi.com> wrote:
>=20
>
> Hi Everyone,
>
>I did a build after removing my .m2 folder and building is failing on :
>
>ExtensionManagerIT.testTrustedExtensionJob:120 NullPointer
>
>Also Falcon-1858 <https://issues.apache.org/jira/browse/FALCON-1858> is a
>backward incompatible as we have changed the default settings, we have not
>mentioned it  in the release notes.
>
>Thanks
>Praveen
>
>On Tue, Jul 26, 2016 at 5:40 AM, Venkat Ranganathan <
>vranganathan@hortonworks.com> wrote:
>
>> Sending Balu=B9s message as text so that the links are not mangled.
>>
>> Venkat
>>
>> On 7/25/16, 4:59 PM, "Balu Vellanki Bala" <bvellanki@hortonworks.com>
>> wrote:
>>
>>    Hello Everyone,
>>
>>
>>    This is the call for vote for the following RC to be released as
>> official Apache Falcon 0.10 release. The source tar ball, signature and
>> checksum files can be downloaded from
>>=20
>>https://dist.apache.org/repos/dist/dev/falcon/apache-falcon-0.10-sources/
>>
>>    You can find the signing key here :
>> http://pgp.mit.edu/pks/lookup?op=3Dvindex&search=3D0xF743ABF42E887C76
>>    You can find the KEYS file here:
>> https://dist.apache.org/repos/dist/release/falcon/KEYS
>>    To verify signature:
>>    gpg --verify apache-falcon-0.10-sources.tar.gz.asc
>> apache-falcon-0.10-sources.tar.gz
>>
>>    Git tag commit-id for the release : release-0.10-rc0
>>
>>=20
>>https://git-wip-us.apache.org/repos/asf?p=3Dfalcon.git;a=3Dcommit;h=3D91d=
c204b6
>>0c0403d16899a44d43ce3e22e9c9960
>>
>>
>>    We have closed around several JIRAs as part of this release, the
>> details of which can be found here:
>>
>>=20
>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=3D12334758=
&s
>>tyleName=3DHtml&projectId=3D12314429
>>
>>    Please find the release notes with brief explanation on key changes
>>at
>> JIRA https://issues.apache.org/jira/browse/FALCON-2098
>>
>>    This vote will remain open for at least 72 hours. Please vote on
>> releasing this RC.
>>    <https://issues.apache.org/jira/browse/FALCON-2098>
>>
>>    [ ] +1 approve
>>    [ ] +0 no opinion
>>    [ ] -1 disapprove (and reason why)
>>
>>    +1 from my side
>>
>>    Thank you
>>    Balu Vellanki
>>
>>
>>
>>
>
>--=20
>_____________________________________________________________
>The information contained in this communication is intended solely for
>the=20
>use of the individual or entity to whom it is addressed and others
>authorized to receive it. It may contain confidential or legally
>privileged=20
>information. If you are not the intended recipient you are hereby
>notified=20
>that any disclosure, copying, distribution or taking any action in
>reliance=20
>on the contents of this information is strictly prohibited and may be
>unlawful. If you have received this communication in error, please notify
>us immediately by responding to this email and then delete it from your
>system. The firm is neither liable for the proper and complete
>transmission=20
>of the information contained in this communication nor for any delay in
>its=20
>receipt.
>
> =20