falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Praveen Adlakha <praveen.adla...@inmobi.com>
Subject Re: Tasks remaining for 0.10 release candidate
Date Tue, 19 Jul 2016 16:29:28 GMT
Hi Balu,

She is waiting for someone to merge it in 0.10 branch so that she can pick
it up for testing.Please review and merge.

Thanks
Praveen

On Tue, Jul 19, 2016 at 9:31 PM, Balu Vellanki Bala <
bvellanki@hortonworks.com> wrote:

> Hi Praveen
>
> I am not sure what you mean. Do you mean to say Pragya tested the fix, so
> I should commit the pull request and create an RC?
>
> Thanks
> Balu
>
> On 7/19/16, 4:56 AM, "Praveen Adlakha" <praveen.adlakha@inmobi.com> wrote:
>
> >Hi Balu,
> >
> >Have fixed the blocker raised by Pragya and has done the required testing.
> >Please have a look and do the needful.
> >
> >Thanks
> >Praveen
> >
> >On Tue, Jul 19, 2016 at 12:55 PM, pragya mittal
> ><mittal.pragya23@gmail.com>
> >wrote:
> >
> >> Hi Balu,
> >>
> >> Sorry for the last minute update. Noticed a blocker for feed submission
> >>in
> >> distributed mode. Please hold the RCA for now.
> >> https://issues.apache.org/jira/browse/FALCON-2088
> >>
> >> Thanks,
> >> Pragya Mittal
> >>
> >> On Tue, Jul 19, 2016 at 2:25 AM, Balu Vellanki Bala <
> >> bvellanki@hortonworks.com> wrote:
> >>
> >> > Thank you Pragya
> >> >
> >> > Balu V
> >> >
> >> > On 7/18/16, 1:39 PM, "pragya mittal" <mittal.pragya23@gmail.com>
> >>wrote:
> >> >
> >> > >Hi Balu,
> >> > >
> >> > >Please go forward with 0.10 release.
> >> > >
> >> > >Thanks,
> >> > >Pragya Mittal
> >> > >
> >> > >On Mon, Jul 18, 2016 at 8:56 PM, Balu Vellanki Bala <
> >> > >bvellanki@hortonworks.com> wrote:
> >> > >
> >> > >> Hi Ajay
> >> > >>
> >> > >> Next one is on 26th Tuesday evening 9PM pacific time and 27th,
Wed
> >> > >>morning
> >> > >> India time
> >> > >>
> >> > >> Balu
> >> > >>
> >> > >> On 7/18/16, 4:07 AM, "Ajay Yadava" <ajayyadavaatos@gmail.com>
> >>wrote:
> >> > >>
> >> > >> >Hi All,
> >> > >> >
> >> > >> >When is the next fortnightly syncup?
> >> > >> >
> >> > >> >On Mon, Jul 18, 2016 at 12:56 PM Balu Vellanki Bala <
> >> > >> >bvellanki@hortonworks.com> wrote:
> >> > >> >
> >> > >> >> Hi Pragya and team
> >> > >> >>
> >> > >> >> At this point all issues have been fixed on 0.10 and
you I am
> >> hoping
> >> > >>you
> >> > >> >> had time to verify that there are no more issues. I will
create
> >> RC-0
> >> > >> >> Monday pacific time.
> >> > >> >>
> >> > >> >> Thank you
> >> > >> >> Balu Vellanki
> >> > >> >>
> >> > >> >> On 7/14/16, 5:54 AM, "Pallavi Rao" <pallavi.rao@inmobi.com>
> >>wrote:
> >> > >> >>
> >> > >> >> >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
<
> >> > >> >> >vranganathan@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"
> >> > >><bvellanki@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.
> >> > >> >>
> >> > >> >> --
> >> > >> >Regards
> >> > >> >Ajay Yadava
> >> > >>
> >> > >>
> >> >
> >> >
> >>
> >
> >--
> >_____________________________________________________________
> >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.
>
>

-- 
_____________________________________________________________
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.

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