Or we perhaps wait until we stabilize trunk first. Given that PIG-3591 is necessary to implement a non-MR execution engine, it would make sense to include it in addition to PIG-3419 in 0.13. Furthermore, I'm refactoring ScriptState class while implementing PPNL for Tez. If we want to avoid API changes after 0.13, we might spend more time before the release.
On Thu, Apr 10, 2014 at 7:26 PM, Daniel Dai <da...@hortonworks.com> wrote: > If we are going to release 0.13.0 in 1-2 months time frame, we shall > definitely branch before check in PIG-3591. PIG-3591 could introduce > regressions and we need time to stabilize it. > > Thanks, > Daniel > > On Thu, Apr 10, 2014 at 4:52 PM, Rohini Palaniswamy > <rohini.adi...@gmail.com> wrote: > > Aniket wanted to make a 0.13 release. Recently we checked in > > PIG-3591: Refactor POPackage to separate MR specific code from packaging > ( > > http://svn.apache.org/viewvc?view=revision&revision=1585283) which is a > lot > > of change. I think we should create the branch-0.13 before this revision > > and start putting only important or critical patches in 0.13 there after. > > Thoughts? > > > > Regards, > > Rohini > > -- > 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. >
