If you happen to know which committers tend to do a lot of code reviews in the specific area of the code covered by your patch, then tagging them in a jira comment is an effective approach. If you're unsure who to contact, then please feel free to email the appropriate project-specific *-dev list for help.
I agree that our jira metadata can be messy, and that can make it challenging to find issues that really do need work. The committers have some efforts under way now to try to keep our bug tracking cleaner. One specific thing we can all do in this area is to apply the "newbie" label to appropriate issues, so that new contributors can run an easy jira query. Meanwhile, if there is every any doubt, please feel free to ask committers. In the case of HADOOP-10861, I think the right approach is to review the current web UI code, and if there are no occurrences of invalid HTML, then the issue can be resolved as Not a Problem. Chris Nauroth Hortonworks http://hortonworks.com/ On 4/23/15, 12:53 AM, "Darrell Taylor" <darrell.tay...@gmail.com> wrote: >Hi Tsuyoshi >On Wed, Apr 22, 2015 at 9:16 AM, Tsuyoshi Ozawa <oz...@apache.org> wrote: > >> Hi Darrell, >> >> Thank you for having interest for contributions to Hadoop project! >> >> > * How do I know if a newbie Jira is even still valid? >> >> Please ping committers whether the issue is valid when the issue looks >> to have been resolved already. >> > >What is the recommended way to do this? Tag them in a Jira comment? Send >a message to the mailing list? > > >> >> > * Does anybody have any suggestions for a suitable newbie ticket to >>pick >> up? >> >> One suggestion from me is to use JQL on JIRA to find issues for newbie. >> If you run following query, you will find fresh and open issues. >> >> project = "Hadoop Common" and labels = "newbie" and status = open >> ORDER BY updatedDate >> > >I have already been looking through these from a link Allen sent me, but >this is what prompted my previous post. It's hard to tell if something >has >been done elsewhere, e.g. HADOOP-10861 > > >> >> Also I think one good starting point is to fix documentation, typos in >> code, trivial changes, or something. >> > >OK, I'll take another sweep through and see what I can find. > >Thanks >Darrell > > > >> >> Thanks, >> - Tsuyoshi >> >> >> On Wed, Apr 22, 2015 at 4:47 PM, Darrell Taylor >> <darrell.tay...@gmail.com> wrote: >> > Hi All, >> > >> > First off I've submitted a patch for HADOOP-11813 as a starter for 10, >> this >> > was an easy change and starts to get me familiar with where things >>are. >> > >> > Now I've been looking through the newbie Jira's to see what else I >>can do >> > to help, but I'm struggling to see the wood for the trees, which I >> suspect >> > is down to my lack of knowledge around how things hang together. >> > >> > I figured I'd go for some easy stuff to start with, so had a look at >> > HADOOP-10861. Most of the html I can find >> > under /hadoop-hdfs-project/hadoop-hdfs/src/main/webapps seems to be >> valid. >> > After further digging I found HDFS-274 which appears to be a patch for >> the >> > pages when they were .jsp instead of html, so does this just need >> closing? >> > >> > So essentially this boils down to two mains questions: >> > >> > * How do I know if a newbie Jira is even still valid? >> > * Does anybody have any suggestions for a suitable newbie ticket to >>pick >> up? >> > >> > Thanks >> > Darrell >>
