+1 to get the usability changes to users quickly. I would also like to get the YARN timeline server integration and staging directory cleanup as part of the 0.5.0 release and will update jiras accordingly ( assuming no one has any concerns ). The timeline server change will move the hadoop dependency to 2.4.0 - is that a concern for anyone? However, there will still remain a capability to compile against hadoop-2.2 ( but the default will change to 2.4 ) .
We should also look at making this release with convenience binary artifacts. This will require some work to get the NOTICE and LICENSE files for the binary tar ball correctly setup. — Hitesh On May 16, 2014, at 11:49 AM, Bikas Saha <[email protected]> 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.
