Re: List volume and issue tracking

Hi All, Per discussion on the JIRA ticket [1], Infra cannot differentiate different types of github notices, so all github notices for PRs and Issues must go to the same list. So the finally solution here is: dev@ -- the development community's discussions commits@ -- commit emails

Re: List volume and issue tracking

Hi mentors, JIRA ticket has been created here: https://issues.apache.org/jira/browse/INFRA-16330 Please help to create notification@ list. On Wed, Apr 11, 2018 at 3:25 PM, Huxing Zhang wrote: > Hi All, > > 72 hours has passed, the following votes were cast: > > Binding: >

Re: List volume and issue tracking

Hi All, 72 hours has passed, the following votes were cast: Binding: +1: Huxing Zhang, Wang Xin, Ian Luo, Mercy Ma Non-Binding: +1: shang zonghai, Yong Zhu, wanhuhou, Minxuan Zhuang The vote therefore passes. I will request the infra to split the traffic. On Mon, Apr 9, 2018 at 10:06 AM,

Re: List volume and issue tracking

Just wondering, does anyone care what the new list is called? Does using notifications@ for now make the most sense, and potentially split that even further? FWIW, this isn't the only project I'm seeing this with. We may need to change some of our podling setup processes to account for the

Re: List volume and issue tracking

+1 On Sun, Apr 8, 2018 at 3:08 PM, shang zonghai wrote: > +1 > > Kind regards, > yiji >

Re: List volume and issue tracking

+1 Kind regards, yiji

Re: List volume and issue tracking

gmail.com>; us...@infra.apache.org<us...@infra.apache.org>主　题：Re: List volume and issue tracking+1，It’s good. dev@ -- the development community's discussions commits@ -- commit emails issues@ -- all emails related to issues (GitHub/Jira) notifications@ -- PR notifications, etc Xin W

Re: List volume and issue tracking

gt; 14:50:53收件人：dev@dubbo.apache.org<dev@dubbo.apache.org>抄　送：Ian > Luo<ian@gmail.com>; us...@infra.apache.org<us...@infra.apache.org>主　题：Re: > List volume and issue tracking+1，It’s good. > dev@ -- the development community's discussions > commits@ -- co

Re: Re: List volume and issue tracking

+1 from Alimail Windows--发件人：Wang Xin<lovep...@hotmail.com>日　期：2018年04月08日 14:50:53收件人：dev@dubbo.apache.org<dev@dubbo.apache.org>抄　送：Ian Luo<ian@gmail.com>; us...@infra.apache.org<us...@infra.apache.org

Re: List volume and issue tracking

+1，It’s good. dev@ -- the development community's discussions commits@ -- commit emails issues@ -- all emails related to issues (GitHub/Jira) notifications@ -- PR notifications, etc Xin Wang lovep...@hotmail.com 在 2018年4月8日，下午2:40，Yong Zhu

Re: List volume and issue tracking

I was also confused by a lot of mixed emails. For this topic, I have the following suggestions: 1. All pull requests are sent to the current dev@dubbo.apache.org. Pr contains final solution to problem solution or feature enhancement capabilities, all users and

Re: List volume and issue tracking

+1 This breakdown looks good to me. On Sun, Apr 8, 2018 at 2:25 PM, Greg Stein wrote: > Many projects choose this pattern: > > dev@ -- the development community's discussions > commits@ -- commit emails > issues@ -- all emails related to issues (GitHub/Jira) > notifications@

Re: List volume and issue tracking

Many projects choose this pattern: dev@ -- the development community's discussions commits@ -- commit emails issues@ -- all emails related to issues (GitHub/Jira) notifications@ -- PR notifications, etc All GitHub activity is required to be delivered to an ASF mailing list. It is up to the

Re: List volume and issue tracking

I think this can be solved by distinguishing github notifications from regular dev@dubbo.apache.org traffic. For github notifications, including issue and pull request, the update message should only go to the interested parties who are involved in this particular topic, but @dev should never be

Re: List volume and issue tracking

Hi, I am +1 on split the traffic of @dev list. The issue appears after migrating repo to ASF. I use "label:asf-dubbo-dev -[github]" to filter out them. :( On Tue, Apr 3, 2018 at 5:06 PM, Yong Zhu wrote: > I have the same feeling. > > IMO, all the issue emails should be

Re: List volume and issue tracking

I have the same feeling. IMO, all the issue emails should be sent to iss...@dubbo.apache.org, all the PR emails should be sent to comm...@dubbo.apache.org. How do you think? and who can help to fix this? And I think we should use github issues, and move all the Jira issues to github. 2018-04-03