Re: Ready for review?

2011-01-07 Thread Niels Basjes
Hi Jakob, Thanks for clarifying this to me. Niels 2011/1/7 Jakob Homan : > Niels- >   Thanks for the contribution.  For the moment your task is done. > Now it's up to a committer to review the patch and, either provide you > with feedback for its improvement, or commit it.  It's in the patch > a

Re: Ready for review?

2011-01-07 Thread Jakob Homan
Niels- Thanks for the contribution. For the moment your task is done. Now it's up to a committer to review the patch and, either provide you with feedback for its improvement, or commit it. It's in the patch available state, which is the flag for reviewers to know there's work for them to do.

Re: svn commit: r1055684 - /hadoop/common/branches/branch-0.20/CHANGES.txt

2011-01-07 Thread Ian Holsman
On Jan 8, 2011, at 4:44 AM, Owen O'Malley wrote: > > To prevent future race conditions, let me formally be the RM for 0.20.3. > Please check with me before any commits to the 0.20 branch. > Great news.. Thanks Owen. > -- Owen

Re: svn commit: r1055684 - /hadoop/common/branches/branch-0.20/CHANGES.txt

2011-01-07 Thread Owen O'Malley
On Jan 5, 2011, at 3:58 PM, Ian Holsman wrote: Is 20.3 a 'dead' release ? I haven't seen any discussion of this on the apache lists about creating a 20.3 release, and kind of goes against all the discussion that we recently had with StAck about creating a 'append' release on 0.20. It i

Ready for review?

2011-01-07 Thread Niels Basjes
Hi, I consider the patch I created to be ready for review by a code reviewer. It does what I want it to do and Hudson gives an overall +1. The http://wiki.apache.org/hadoop/HowToContribute was unclear to me on what to do next. So, what should I do? Simply wait / change the stated of the issue /