Right. Review is important as mush as development. We have to review more patches as soon as possible.
For the faster and easier review, I have two following suggestions. - First, we have to write very detailed issue descriptions. It would be best if anyone who has not ever thought about that issue can understand. - Second, every patch should involve an enough amount of comments on important portions. It is also be great if the reviewer can understand the contributor's intentions such as the problem solving approach, detailed decription of algorithms, and overall mechanisms. I think that these will improve our rewiew process much better. Best regards, Jihoon On Tue, Mar 17, 2015 at 3:10 PM Hyunsik Choi <[email protected]> wrote: > Hi folks, > > Please see the pull list request. Many reviews are pending. Why is > this problem getting severe in these days? > > Honestly, I have consumed most of of patch reviews 1 month ago. In > these days, I cannot spend my time on Tajo. Unfortunately, I won't for > few weeks more. > > As you can see 'What are the responsibilities of a Committer?' at > http://www.apache.org/dev/committers.html#committer-responsibilities, > committers and PMC's have the responsibility to review the patches. I > suggest that you guys should spend some of your time on reviews. > > In addition, reviews would be good for contributors who want to become > committers because reviews are also one of important factors that > measure his or her contributions. > > Best regards, > Hyunsik >
