Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Pig, mail # dev - Are we ready for Pig 0.12.0 release?


Copy link to this message
-
Re: Are we ready for Pig 0.12.0 release?
Prashant Kommireddi 2013-09-03, 18:36
+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 <[EMAIL PROTECTED]>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 <[EMAIL PROTECTED]>
> 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.
> > >
>