Balu, et. al,
The status of the blocker bugs raised by Pragya are as follows:
FALCON-2070 - Resolved as Invalid
FALCON-2076, FALCON-1749, FALCON-2067  - Merged to trunk and 0.10
FALCON-2060 - In progress. Should be done by morrow.

Once FALCON-2060 is merged, Pragya can do the final verification and
sign-off.

Thanks,
Pallavi


On Wed, Jul 13, 2016 at 12:24 PM, Venkat Ranganathan <
vranganat...@hortonworks.com> wrote:

> Thanks Balu
>
> Sorry I missed the  meeting.   I was stuck in another work session and
> could not get out of it quickly.
>
> It looks like we are converging.   Hopefully we should be able to do a RC
> for voting this week!
>
> Thanks
>
> Venkat
>
>
> On 7/12/16, 9:50 PM, "Balu Vellanki Bala" <bvella...@hortonworks.com>
> wrote:
>
> Hi Team,
>
> We had bi-weekly Falcon collaboration meeting and discussed the 0.10
> release candidate. The following tasks came out of meeting,
>
>
>   1.  Pragya opened Jiras for issues that caused regression or feature
> failure in 0.10. Pallavi and Balu to work on these issues within next two
> days.
>   2.  Balu will update 0.9 Jiras to be Apache Yetus compliant
>   3.  Regenerate changelog for Apache Falcon branches.
>   4.  Pragya to re-run the regression tests asap after tasks 1 and 3 are
> done.
>
> We hope to have a release candidate by Friday pacific time if all goes
> well,
> Thank you
> Balu Vellanki
>
>
>

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
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 
of the information contained in this communication nor for any delay in its 
receipt.

Reply via email to