Here's a git branch with the backported changes in case anyone has time to take a look this weekend:
https://github.com/toddlipcon/hadoop-common/tree/branch-2-QJM There were a few conflicts due to patches committed in different orders, and I had to pull in a couple other JIRAs along the way, but it is passing its tests. If it looks good I'll start putting up the patches on JIRA and committing next week. -Todd On Fri, Nov 16, 2012 at 1:14 PM, Todd Lipcon <t...@cloudera.com> wrote: > +1 from me, too. I wanted to let it sit in trunk for a few weeks to see if > anyone found issues, but it's now been a bit over a month all the feedback > I've gotten so far has been good, tests have been stable, etc. > > Unless anyone votes otherwise, I'll start backporting the patches into > branch-2. > > Todd > > On Fri, Nov 16, 2012 at 12:58 PM, lohit <lohit.vijayar...@gmail.com>wrote: > >> +1 on having QJM in hadoop-2.0.3. Any rough estimate when this is targeted >> for? >> >> 2012/11/15 Arun C Murthy <a...@hortonworks.com> >> >> > On the heels of the planned 0.23.5 release (thanks Bobby & Thomas) I >> want >> > to rollout a hadoop-2.0.3 release to reflect the growing stability of >> YARN. >> > >> > I'm hoping we can also release the QJM along-with; hence I'd love to >> know >> > an ETA - Todd? Sanjay? Suresh? >> > >> > One other thing which would be nice henceforth is to better reflect >> > release content for end-users in release-notes etc.; thus, can I ask >> > committers to start paying closer attention to bug classification such >> as >> > Blocker/Critical/Major/Minor etc.? This way, as we get closer to stable >> > hadoop-2 releases, we can do a better job communicating content and it's >> > criticality. >> > >> > thanks, >> > Arun >> > >> > >> >> >> -- >> Have a Nice Day! >> Lohit >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera > -- Todd Lipcon Software Engineer, Cloudera
