Can I add PIG-3967 (patch available)? I can run e2e tests once these patches are in. June 3rd sounds good to me.
On Wed, May 28, 2014 at 5:37 PM, Aniket Mokashi <[email protected]> wrote: > We are down to just 4 jiras now: > > - PIG-3739 <https://issues.apache.org/jira/browse/PIG-3739> (Aniket to > submit a fix) > - PIG-3800 <https://issues.apache.org/jira/browse/PIG-3800> (Prashant to > commit) > - PIG-3874 <https://issues.apache.org/jira/browse/PIG-3874> (Aniket to > rebase and commit) > - PIG-3892 <https://issues.apache.org/jira/browse/PIG-3892> (Daniel) > > Daniel, Cheolsoo, do you have bw to run e2e once we get these changes in? > Any other blockers on the release? > > How about targeting June 3rd for the pig 0.13 RC? > > Thanks, > Aniket > > > > On Wed, May 28, 2014 at 9:35 AM, Lorand Bendig <[email protected]> wrote: > >> Thank you, Aniket! >> --Lorand >> >> >> On 05/28/2014 05:21 PM, Aniket Mokashi wrote: >> >>> Thanks Lorand. I committed the fix for PIG-3966 to branch-0.13 and trunk. >>> >>> Thanks, >>> Aniket >>> >>> >>> On Wed, May 28, 2014 at 6:31 AM, Lorand Bendig <[email protected]> wrote: >>> >>> I'd like to have PIG-3966 for 0.13.0 . >>>> >>>> Thanks, >>>> Lorand >>>> >>>> >>>> On 05/28/2014 12:29 AM, Aniket Mokashi wrote: >>>> >>>> Thanks Daniel and Cheolsoo. I've moved the jiras to right version >>>>> accordingly. >>>>> >>>>> We have following jiras left before we can make a release- >>>>> - PIG-3739 <https://issues.apache.org/jira/browse/PIG-3739> (Aniket to >>>>> submit patch) >>>>> - PIG-3752 <https://issues.apache.org/jira/browse/PIG-3752> (Daniel) >>>>> - PIG-3800 <https://issues.apache.org/jira/browse/PIG-3800> (Prashant) >>>>> - <https://issues.apache.org/jira/browse/PIG-3830>PIG-3874< >>>>> https://issues.apache.org/jira/browse/PIG-3874> >>>>> (To >>>>> review) >>>>> - PIG-3892 <https://issues.apache.org/jira/browse/PIG-3892> (Daniel) >>>>> - PIG-3954 <https://issues.apache.org/jira/browse/PIG-3954> (Aniket) >>>>> - PIG-3958 <https://issues.apache.org/jira/browse/PIG-3958> (Aniket to >>>>> fix >>>>> the regression) >>>>> - PIG-3955 <https://issues.apache.org/jira/browse/PIG-3955> (Aniket) >>>>> >>>>> - Any other? >>>>> >>>>> Thanks, >>>>> Aniket >>>>> >>>>> >>>>> On Mon, May 26, 2014 at 12:56 AM, Daniel Dai <[email protected]> >>>>> wrote: >>>>> >>>>> Thanks a lot! >>>>> >>>>>> On Sun, May 25, 2014 at 6:41 PM, Cheolsoo Park <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi Daniel, >>>>>>> >>>>>>> I reviewed PIG-3949, 3513, and 3892. I'll leave Windows patches to >>>>>>> >>>>>>> someone >>>>>> >>>>>> who has access to Windows. >>>>>>> >>>>>>> Thanks, >>>>>>> Cheolsoo >>>>>>> >>>>>>> >>>>>>> On Sun, May 25, 2014 at 7:07 PM, Daniel Dai <[email protected]> >>>>>>> >>>>>>> wrote: >>>>>> >>>>>> Thanks, besides unit/e2e tests , we will need to add documentation of >>>>>>> >>>>>>>> new feature: >>>>>>>> >>>>>>>> PIG-3954 Document use of user level jar cache >>>>>>>> PIG-3800 Documentation for Pig whitelist and blacklist features >>>>>>>> >>>>>>>> I will also try to get these patches in if someone can help review: >>>>>>>> PIG-3949 HiveColumnarStorage compile failure with Hive 0.13.0 >>>>>>>> (trivial) >>>>>>>> PIG-3513 Upgrade snappy.java to 1.1.0-M4 (trivial) >>>>>>>> PIG-3752 Fix e2e Parallel test for Windows >>>>>>>> PIG-3892 Pig distribution for hadoop 2 >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Daniel >>>>>>>> >>>>>>>> On Sun, May 25, 2014 at 10:39 AM, Cheolsoo Park < >>>>>>>> [email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi Aniket, >>>>>>>>> >>>>>>>>> Thanks a lot for driving the 0.13 release! I think we should get it >>>>>>>>> >>>>>>>>> out >>>>>>>> >>>>>>> as >>>>>>> >>>>>>>> soon as all the unit and e2e tests are fixed. >>>>>>>>> >>>>>>>>> Here are test failures that I am aware of- >>>>>>>>> https://issues.apache.org/jira/browse/PIG-3635 >>>>>>>>> https://issues.apache.org/jira/browse/PIG-3739 >>>>>>>>> https://issues.apache.org/jira/browse/PIG-3958 >>>>>>>>> >>>>>>>>> I will re-run the e2e tests to see whether there is any recent >>>>>>>>> >>>>>>>>> regression. >>>>>>>> >>>>>>>> Thanks, >>>>>>>>> Cheolsoo >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, May 23, 2014 at 7:26 PM, Aniket Mokashi < >>>>>>>>> [email protected]> >>>>>>>>> >>>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>>> >>>>>>>>>> We discussed this few months back and most of the issues we were >>>>>>>>>> >>>>>>>>>> waiting to >>>>>>>>> get in are in trunk now. Should we plan a pig 0.13.0 release in a >>>>>>>>> week >>>>>>>>> >>>>>>>> or >>>>>>> >>>>>>>> so? >>>>>>>>> >>>>>>>>>> There are quite a lot of jiras marked with fixed version 0.13. >>>>>>>>>> >>>>>>>>>> (filter = >>>>>>>>> >>>>>>>> "project = PIG AND fixVersion = 0.13.0 AND resolution = Unresolved >>>>>>> >>>>>>>> ORDER BY >>>>>>>>> due ASC, priority DESC, created ASC"). I will mark these jiras as >>>>>>>>> for >>>>>>>>> 0.14 >>>>>>>>> release now. >>>>>>>>> >>>>>>>>>> If you have patches want to get in, please make sure the Jira >>>>>>>>>> ticket >>>>>>>>>> >>>>>>>>>> has >>>>>>>>> >>>>>>>> fix version set to 0.13. If you have patches that must go in 0.13 >>>>>>> >>>>>>>> branch >>>>>>>>> >>>>>>>> but can wait and need more time, please mark them as version 0.13.1. >>>>>>> >>>>>>>> Let me know if you have any questions/concerns. We can target 2/6 for >>>>>>>>>> >>>>>>>>>> the >>>>>>>>> pig release. Thoughts? >>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Aniket >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>> 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" -- 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.
