pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aniket Mokashi <aniket...@gmail.com>
Subject Re: Plan to merge tez branch into trunk and branch 0.13
Date Mon, 19 May 2014 17:44:58 GMT
Thanks everyone. I will branch out pig 0.13 at 2pm tomorrow. Please let me
know if there are any questions/concerns.

Thanks,
Aniket


On Thu, May 15, 2014 at 2:50 PM, Rohini Palaniswamy <rohini.aditya@gmail.com
> wrote:

> +1 on branching for 0.13 and then merging Tez branch.
>
>
> On Wed, May 14, 2014 at 8:07 AM, Cheolsoo Park <piaozhexiu@gmail.com>
> wrote:
>
> > I'm also +1 on releasing 0.13 and then merging Tez branch.
> >
> >
> > On Tue, May 13, 2014 at 11:52 PM, Prashant Kommireddi
> > <prash1784@gmail.com>wrote:
> >
> > > I'm a +1 on branching 0.13 and merging Tez branch with trunk. That
> would
> > > give us ample time to make 0.14 stable with tez merged.
> > >
> > >
> > > On Tue, May 13, 2014 at 9:05 PM, Daniel Dai <daijy@hortonworks.com>
> > wrote:
> > >
> > > > We will make sure all existing unit tests / e2e tests pass in MR mode
> > > > before merge, but it is possible we might hit some issues which are
> > > > not captured by existing tests after merge. I can hardly tell how
> much
> > > > time will it take to say the codebase is stable enough at this
> moment,
> > > > but it is better to merge to trunk early, so more Pig developers can
> > > > try the merged codebase and have more time to capture issues before
> we
> > > > release Pig with tez (most probably Pig 0.14.0).
> > > >
> > > > Thanks,
> > > > Daniel
> > > >
> > > > On Tue, May 13, 2014 at 3:48 PM, Prashant Kommireddi
> > > > <prash1784@gmail.com> wrote:
> > > > > Hi Daniel,
> > > > >
> > > > > How long do you think might it take for the merge to stabilize?
> > > > >
> > > > > Thanks,
> > > > > Prashant
> > > > >
> > > > >
> > > > > On Tue, May 13, 2014 at 11:47 AM, Daniel Dai <
> daijy@hortonworks.com>
> > > > wrote:
> > > > >
> > > > >> Hi, Pig devs,
> > > > >>
> > > > >> After several months development, Tez branch is becoming stable
> and
> > we
> > > > >> plan to merge tez branch to trunk in the next few weeks.
> > > > >>
> > > > >> Several weeks ago, we have a discussion about branching 0.13,
and
> if
> > > > >> we still have interest to do a release before merging tez, we
> shall
> > do
> > > > >> it now.
> > > > >>
> > > > >> Thoughts?
> > > > >>
> > > > >> Thanks,
> > > > >> Daniel
> > > > >>
> > > > >> --
> > > > >> CONFIDENTIALITY NOTICE
> > > > >> NOTICE: This message is intended for the use of the individual
or
> > > > entity to
> > > > >> which it is addressed and may contain information that is
> > > confidential,
> > > > >> privileged and exempt from disclosure under applicable law. If
the
> > > > reader
> > > > >> of this message is not the intended recipient, you are hereby
> > notified
> > > > that
> > > > >> any printing, copying, dissemination, distribution, disclosure
or
> > > > >> forwarding of this communication is strictly prohibited. If you
> have
> > > > >> received this communication in error, please contact the sender
> > > > immediately
> > > > >> and delete it from your system. Thank You.
> > > > >>
> > > >
> > > > --
> > > > CONFIDENTIALITY NOTICE
> > > > NOTICE: This message is intended for the use of the individual or
> > entity
> > > to
> > > > which it is addressed and may contain information that is
> confidential,
> > > > privileged and exempt from disclosure under applicable law. If the
> > reader
> > > > of this message is not the intended recipient, you are hereby
> notified
> > > that
> > > > any printing, copying, dissemination, distribution, disclosure or
> > > > forwarding of this communication is strictly prohibited. If you have
> > > > received this communication in error, please contact the sender
> > > immediately
> > > > and delete it from your system. Thank You.
> > > >
> > >
> >
>



-- 
"...:::Aniket:::... Quetzalco@tl"

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