I can understand that. However, it does not explain the one that did have a JIRA ID.
If the Hadoop community does not wish to monitor GitHub PRs, it should have INFRA disable them. However, I think it would be better if the community monitored the PRs (or the notification list that the PRs report to)... because that's a really low bar for contributing small changes, and it's a great way to get more developers active and engaged. On Wed, Sep 4, 2019 at 2:55 PM Wei-Chiu Chuang <weic...@apache.org> wrote: > > I sent out a message a few days ago, but I failed to loop in general@ too. > > Basically, if your PR does not have a JIRA ID in the summary, it is very > unlikely to be picked up by committers. Most committers monitor JIRA, not > Github PR. Please follow the How to Contribute wiki so that life is easier > for all. > > On Wed, Sep 4, 2019 at 11:35 AM Christopher <ctubb...@apache.org> wrote: >> >> Hi Hadoop Devs, >> >> Just curious whether we can get some pull requests merged in. Yetus >> will continue to spam open pull requests with walls of text, drowning >> out any potential human conversation. This doesn't seem to be >> particularly helpful in general, but it is especially bad if the pull >> request is open for a long time, and isn't addressed. >> >> Here's a trivial pull request that should be merged to fix a typo in a >> javadoc, but was closed instead of being merged, because of the spam >> and lack of human response: >> >> https://github.com/apache/hadoop/pull/350 >> >> Here's another relatively simple change to support immutable Hadoop >> configuration views (not entirely trivial, but not very difficult, >> either), that was closed, because it was ignored and Yetus got too >> spammy: >> >> https://github.com/apache/hadoop/pull/473 >> (to address https://issues.apache.org/jira/browse/HADOOP-11223) >> >> >> My questions are: >> >> 1. Why is there no active response to users that submit pull requests? >> 2. Does Yetus really need to drown human conversation threads on >> GitHub with walls of automated text? (vs. using the GitHub checks API >> or similar brief status message) >> 3. Can somebody take a look at these two pull requests and merge them >> or explain what is needed to get them merge-ready? >> >> Thanks, >> >> Christopher >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: general-h...@hadoop.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org For additional commands, e-mail: general-h...@hadoop.apache.org
