+1 on the approach too. Here's a link to the 4.1 issues for convenience: http://s.apache.org/oozie4.1
*On the 4 unassigned JIRAs:* OOZIE-1969 and OOZIE-1970 appear to be duplicates from someone who tried to compile against Hadoop 2.4.1. I'll get rid of them shortly. So there's really only 2 unassigned JIRAs: - OOZIE-1625: someone said that hadooplibs 2.2 is pulling in hadoop-auth 2.0.2-alpha, which is weird because we have Hadoop 2.3. In any case, if it's pulling in the wrong hadoop-auth, that's definitely something we should fix - OOZIE-1973, which is about an Exception in the SharelibService. Puru and Shwetha know more about this one. *For the assigned/patch available JIRAs*, we should all make an effort to get those reviewed and committed. - Robert On Wed, Aug 27, 2014 at 7:37 PM, Mohammad Islam <[email protected]> wrote: > +1 to Bowen's approach. > > Regards, > Mohammad > > > On Wednesday, August 27, 2014 2:29 PM, bowen zhang > <[email protected]> wrote: > > > > Hi guys, > According to Issue Navigator - ASF JIRA, we still have 11 items > outstanding for 4.1 release. 4 of the 11 items have no assignees and no > patches. I want to tentatively set next Friday, the 5th, as the deadline > for us to resolve these issues since we cannot let this release dragging on > forever. For tickets with patches available, I think we are pretty close to > the finish line. For the tickets without assignees and patches by then, we > will defer them to the next release unless the reporters can make really > compelling cases to get them in for 4.1. In the assignee section, I see > Purshotam, Robert, Mona. Can every one of you reply to the thread and give > constant updates on the outstanding issues? Let's use this thread for our > 4.1 release status tracking. > Bowen > > > > Issue Navigator - ASF JIRA > Linked Applications Loading…… Dashboards Projects Issues Agile Help Online > Help > View on issues.apache.org Preview by Yahoo >
