tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Eagles <jeag...@gmail.com>
Subject Re: 0.5 incubating release
Date Mon, 19 May 2014 18:26:00 GMT
Agree with all the main points on this thread. Is there any user
documentation that will aide greatly this same principle of making Tez
migration accessible?

jeagles


On Mon, May 19, 2014 at 11:54 AM, Siddharth Seth <sseth@apache.org> wrote:

> Sounds good; getting most of the API changes in place would help downstream
> projects like Hive, Pig and Cascading by allowing them to depend on a
> released version. I don't think we'll be able to get everything done, and
> iterative improvements will continue in subsequent releases, but getting a
> large set of the incompatible changes into a release would be helpful.
>
>
> On Fri, May 16, 2014 at 11:49 AM, Bikas Saha <bikas@hortonworks.com>
> wrote:
>
> > Hi,
> >
> >
> >
> > Given the growing interest in users trying to write Tez jobs, it may make
> > sense to expedite a 0.5 release as soon as possible in order to have a
> > stable vehicle by which we can release the Ease of Use work being tracked
> > by https://issues.apache.org/jira/browse/TEZ-690. This will enable users
> > to
> > start writing their code from a much cleaner base. While API’s and
> helpers
> > will keep evolving, the 0.5 release is trying to target user feedback
> about
> > the most painful parts of writing code against the API’s.
> >
> >
> >
> > On this note, let us all take some time and examine the sub-tasks of
> > https://issues.apache.org/jira/browse/TEZ-690. Please add any items that
> > are currently missing. Please mark critical usability jiras with target
> > version 0.5 so that we can focus on them before the release. Please also
> > help out by picking up the critical jiras and providing patches.
> >
> >
> >
> > Thoughts?
> >
> >
> >
> > Thanks!
> >
> > Bikas
> >
> > --
> > 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.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message