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 <[email protected]> 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
> <[email protected]> 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 <[email protected]>
> 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.
>

Reply via email to