Thanks Daniel.
On Fri, Sep 20, 2013 at 3:37 PM, Daniel Dai <da...@hortonworks.com> wrote: > I just committed PIG-3199. > > > On Fri, Sep 20, 2013 at 3:06 PM, Prashant Kommireddi <prash1...@gmail.com > >wrote: > > > Can we get PIG-3199 in? It only exposes a few properties of LP > (load/store > > paths and funcs) via a wrapper > > > > > > On Fri, Sep 20, 2013 at 3:03 PM, Daniel Dai <da...@hortonworks.com> > wrote: > > > > > With regard to branching 0.12, I will try to commit PIG-2417 and > Cheolsoo > > > will probably commit PIG-3471. After that I will branch 0.12, hopefully > > > over the weekend. Anything I miss? > > > > > > Thanks, > > > Daniel > > > > > > > > > On Tue, Sep 10, 2013 at 11:30 AM, Russell Jurney > > > <russell.jur...@gmail.com>wrote: > > > > > > > +1, I need PIG-2417 too. > > > > > > > > > > > > On Wed, Sep 4, 2013 at 5:17 AM, Jeremy Karn <jk...@mortardata.com> > > > wrote: > > > > > > > > > I have one JIRA https://issues.apache.org/jira/browse/PIG-2417that > > I > > > > > would > > > > > like to get into 0.12 because we've had a number of people ask us > > about > > > > > getting it committed back to Apache. However, if it looks like too > > > much > > > > to > > > > > review and get committed in the next week or two it could probably > be > > > > > pushed off. > > > > > > > > > > I also have 3 small jiras (3426, 3430, 3431) I'd like to get into > > 0.12. > > > > > I'm going to double check the submitted patches today because I > > think > > > > > https://issues.apache.org/jira/browse/PIG-3419 might have broken > the > > > > > currently submitted patches. > > > > > > > > > > > > > > > On Tue, Sep 3, 2013 at 2:36 PM, Prashant Kommireddi < > > > prash1...@gmail.com > > > > > >wrote: > > > > > > > > > > > +1 for a 0.12 release. > > > > > > > > > > > > I have one outstanding JIRA > > > > > https://issues.apache.org/jira/browse/PIG-3199 > > > > > > . > > > > > > Cheolsoo was fine with the patch (except for a typo which I will > > > > correct) > > > > > > but wanted a second opinion. Can someone please take a look? > > > > > > > > > > > > > > > > > > On Tue, Sep 3, 2013 at 11:08 AM, Jarek Jarcec Cecho < > > > jar...@apache.org > > > > > > >wrote: > > > > > > > > > > > > > I'll try to clean up and finish PIG-3390 (HBase 0.95 support) > > this > > > > > week, > > > > > > > to see if it can be included. > > > > > > > > > > > > > > Jarcec > > > > > > > > > > > > > > On Tue, Sep 03, 2013 at 10:56:42AM -0700, Cheolsoo Park wrote: > > > > > > > > +1. I will go through my jiras this week. > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Sep 3, 2013 at 10:34 AM, Daniel Dai < > > > da...@hortonworks.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi, All, > > > > > > > > > It has been more than half a year since initial Pig 0.11 > > > release. > > > > > I'd > > > > > > > like > > > > > > > > > roll a Pig 0.12 release around the end of September or the > > > > > beginning > > > > > > of > > > > > > > > > October. Let me know if it is possible. > > > > > > > > > > > > > > > > > > Proposed schedule: > > > > > > > > > 1. Commit all major features (1-2 weeks) > > > > > > > > > 2. Branching Pig 0.12 > > > > > > > > > 3. Commit remaining patches (1-2 weeks) > > > > > > > > > 4. Wrapping up, document (1 week) > > > > > > > > > > > > > > > > > > If you have patches want to get in, please make sure the > Jira > > > > > ticket > > > > > > > has > > > > > > > > > fix version set to 0.12. If the patches originally set to > > 0.12 > > > > and > > > > > > you > > > > > > > > > think you can delay, please mark the fix version to either > > > 0.13.0 > > > > > or > > > > > > > > > 0.12.1. > > > > > > > > > > > > > > > > > > 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. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Jeremy Karn / Lead Developer > > > > > MORTAR DATA / 519 277 4391 / www.mortardata.com > > > > > > > > > > > > > > > > > > > > > -- > > > > Russell Jurney twitter.com/rjurney russell.jur...@gmail.com > > > > datasyndrome.com > > > > > > > > > > -- > > > 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. >
