I committed the following patches today: HADOOP-10086 HADOOP-9982 HADOOP-10212 HDFS-5297
Remaining from your initial list: HADOOP-10139 - needs to be rebased HDFS-5492 - I will review it this week. HADOOP-6350 - not sure of the status. Is the attached patch ready for review? I will look at the other common/HDFS patches as I get time after this week, unless another committer wants to take a look. Arpit On Wed, Jan 22, 2014 at 2:40 AM, Akira AJISAKA <ajisa...@oss.nttdata.co.jp>wrote: > >> Akira, could you please resend a list of your patches that need > reviewing > >> if you have it handy. > > Here is the list of all the documentation patches I have. > > > https://issues.apache.org/jira/browse/HADOOP-6350?jql= > project%20in%20(HADOOP%2C%20YARN%2C%20HDFS%2C%20MAPREDUCE)%20AND% > 20resolution%20%3D%20Unresolved%20AND%20component%20%3D% > 20documentation%20AND%20status%20%3D%20%22Patch%20Available%22%20AND% > 20assignee%20in%20(ajisakaa)%20ORDER%20BY%20priority%20DESC > > In the above list, the JIRAs I think high priority are as follows: > > * HADOOP-6350 > * HADOOP-9982 > * HADOOP-10139 > * HADOOP-10212 > * YARN-1531 > * HDFS-5297 > * HDFS-5492 > * MAPREDUCE-4282 > > I will appreciate your reviews. > > Thanks, > Akira > > > (2014/01/22 13:17), Masatake Iwasaki wrote: > >> > I will review >> HADOOP-10086<https://issues.apache.org/jira/browse/HADOOP-10086>this >> > week unless another committer gets to it first. >> >> I appreciate it Arpit! >> >> >> > Thanks for your efforts to clean up the documentation. Unfortunately >> some >> > fixes can get lost in the noise and this is true not just for >> documentation >> > fixes, so thanks for bringing these to our attention. >> >> I will do what I can do to improve this. Such as helping review process. >> >> >> Regards, >> Masatake Iwasaki >> >> >> (2014/01/22 3:22), Arpit Agarwal wrote: >> >>> I will review >>> HADOOP-10086<https://issues.apache.org/jira/browse/HADOOP-10086>this >>> week unless another committer gets to it first. >>> >>> Akira, could you please resend a list of your patches that need reviewing >>> if you have it handy. >>> >>> Thanks for your efforts to clean up the documentation. Unfortunately some >>> fixes can get lost in the noise and this is true not just for >>> documentation >>> fixes, so thanks for bringing these to our attention. >>> >>> Regards, >>> Arpit >>> >>> >>> >>> >>> On Mon, Jan 20, 2014 at 11:47 PM, Akira AJISAKA >>> <ajisa...@oss.nttdata.co.jp>wrote: >>> >>> Hi All, >>>> >>>> I wrote several patches for documentation >>>> but most of them are not reviewed. >>>> >>>> I want to improve not only the new features but also >>>> the documents. I also think the documents are not >>>> well maintained mainly because : >>>> >>>> * Deprecated commands and parameters still exist. >>>> * Undocumented command options exist. >>>> * There're a lot of dead links. >>>> >>>> I'll be happy when the above problems are fixed for 2.4 release. >>>> I'm waiting for your advices and reviews! >>>> >>>> Thanks Masatake for this proposal. >>>> >>>> Regards, >>>> Akira >>>> >>>> (2014/01/21 9:03), Masatake Iwasaki wrote: >>>> >>>>> Hi developers, >>>>> >>>>> I wrote a patch for Hadoop's site documentation and would like reviews. >>>>> https://issues.apache.org/jira/browse/HADOOP-10086 >>>>> >>>>> Though I would like to fix documentation further, >>>>> there seems to be many open JIRA issues concerning documents. >>>>> I think the documents is not well maintained now >>>>> because the documentation work does not tend to get >>>>> enough attention of reviewers and commiters. >>>>> >>>>> In order to impove the situation, >>>>> should I write Wiki pages rather than site documentation >>>>> or refactor whole documentation structure >>>>> in the way like HBase book (http://hbase.apache.org/book/book.html)? >>>>> >>>>> I will appreciate your advices. >>>>> >>>>> Regards, >>>>> Masatake Iwasaki >>>>> >>>>> >>>> >>>> >>> >> > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
