Hi Jason,
I assume the 0.12 branch creation does not have to wait for this, and you
just want it to be included in the release.
Thanks,
Thejas



On Fri, Aug 30, 2013 at 4:26 PM, Jason Dere <jd...@hortonworks.com> wrote:

> Would like to see HIVE-4844 make it in if possible.
>
> Thanks,
> Jason
>
> On Aug 29, 2013, at 10:31 PM, Eugene Koifman <ekoif...@hortonworks.com>
> wrote:
>
> > I think we should make sure that several items under HIVE-4869 get
> checked
> > in before branching.
> >
> > Eugene
> >
> >
> > On Thu, Aug 29, 2013 at 9:18 PM, Thejas Nair <the...@hortonworks.com>
> wrote:
> >
> >> It has been more than 3 months since 0.11 was released and we already
> have
> >> 294 jiras in resolved-fixed state for 0.12. This includes several new
> >> features such as date data type, optimizer improvements, ORC format
> >> improvements and many bug fixes. There are also many features look
> ready to
> >> get committed soon such as the varchar type.
> >> I think it is time to start preparing for a 0.12 release by creating a
> >> branch later next week and start stabilizing it. What do people think
> about
> >> it ?
> >>
> >> As we get closer to the branching, we can start discussing any
> additional
> >> features/bug fixes that we should add to the release and start
> monitoring
> >> their progress.
> >>
> >> Thanks,
> >> Thejas
> >>
> >> --
> >> 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.
>
>
> --
> 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