@Jon, one option could be that we can punt all of the jiras to 0.6.3 ( assuming you have the bandwidth to a 0.6.2 release )?
As per the comments by @Jeff on TEZ-2311, it seems to be non-trivial. In any case, will take a look at it again today with Jeff in more detail and update on whether it is doable in a short turnaround time. If not, we can consider moving it to 0.6.3? thanks — Hitesh On Jul 23, 2015, at 8:28 AM, Jonathan Eagles <[email protected]> wrote: > TEZ-2311 is the most critical of the list. If this goes in today I can > start the release process for 0.6.2 > > On Wed, Jul 22, 2015 at 1:14 PM, Hitesh Shah <[email protected]> wrote: >> Looking at >> "https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20%22Target%20Version%2Fs%22%20%3D%200.6.2%20ORDER%20BY%20priority%20DESC” >> : >> >> It seems like there are only 5 jiras - most of which are non-critical to >> functionality except for TEZ-2311 ( which happens only in some cases after >> AM crashes ). >> >> We can probably move all of them to target 0.6.3 instead if a 0.6.2 release >> is needed before the fixes are available. >> >> @Jeff, @Jon - any comments? >> >> thanks >> — Hitesh >> >> >> On Jul 22, 2015, at 10:10 AM, Chris K Wensel <[email protected]> wrote: >> >>> +1 obviously >>> >>>> On Jul 21, 2015, at 10:33 AM, Andre Kelpe <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> we would like to as the Tez community to do a 0.6.2 release of Tez, so that >>>> we are able to release Lingual, our SQL engine on top of Cascading with Tez >>>> support. >>>> >>>> We have been blocked by the thread hangs, but since >>>> https://issues.apache.org/jira/browse/TEZ-2475 is resolved, things look >>>> good to us. The thing is of course, that we can't release with a SNAPSHOT >>>> dependency on Tez, so it would be great if you could do a 0.6.2 release. >>>> >>>> I believe the scalding on Tez effort wold also benefit from that. >>>> >>>> Thanks! >>>> >>>> - Anrdré >>>> >>>> -- >>>> André Kelpe >>>> [email protected] >>>> http://concurrentinc.com >>> >>> — >>> Chris K Wensel >>> [email protected] >>> >>> >>> >>> >>
