I believe we can disregard MAPREDUCE-4820 since MAPREDUCE-4549 is already in branch-2. FYI.
On Jan 29, 2013, at 8:51 AM, Roman Shaposhnik wrote: > On Mon, Jan 28, 2013 at 3:11 PM, Roman Shaposhnik <[email protected]> wrote: >> Hi Arun, >> >> On Wed, Jan 16, 2013 at 6:52 AM, Arun C Murthy <[email protected]> wrote: >>> Happy new year folks! >>> >>> I'm glad to see that we are down to the last couple of blockers I hope we >>> can resolve in the next 24-hrs or so. >>> >>> Once done, I'll create a branch-2.0.3-alpha to unblock branch-2 >>> for commits targeted towards the next release, create the new fix-versions >>> in jira and spin the RC. >> >> Quick question -- when do you think you can have the >> branch-2.0.3-alpha in place? >> >> We'd *really* like to start testing it in Bigtop ASAP (Bigtop 0.6.0 is >> supposed to be >> based on Hadoop 2.0.3) so we can avoid integration issues like we had between >> 2.0.2 and Oozie. >> >> Any help in making it available to us sooner would be greatly appreciated! > > On top of that I'd like to nominate: > https://issues.apache.org/jira/browse/MAPREDUCE-4820 > as a blocker. For as long as it is not fixed Oozie is unusable with > Hadoop 2.0.[23]. > > Thanks, > Roman. -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
