dubbo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yong Zhu <diecui1...@gmail.com>
Subject Re: List volume and issue tracking
Date Tue, 03 Apr 2018 09:06:21 GMT
I have the same feeling.

IMO, all the issue emails should be sent to issues@dubbo.apache.org, all
the PR emails should be sent to commits@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 16:43 GMT+08:00 Mark Thomas <markt@apache.org>:

> All,
>
> I've been away for just over a week and come back to find over 300
> unread emails on the dev list.
>
> A large proportion of these messages are comments on pull requests? Is
> dev@ the right list for those?
>
> Another large proportion appear to be comments on issues? Is dev@ the
> right list for those?
>
> Generally, the recommendation is to split into multiple lists based on
> audience rather than topic. For some projects it therefore makes sense
> to have all dev related traffic going to a single list. For others,
> particularly large projects, it makes sense to split the dev traffic.
>
> The project appears to be using GitHub issues and Jira. That is
> confusing. I'd recommend that you select one issue tracker and stick to it.
>
> Finally, the github issues seem to be a mix of bugs and support
> questions. Is that the way the podling wants to use github issues?
>
> I have no view on what the 'right' answers to the above questions are.
> I'm asking them to get the podling thinking about the issues. What, if
> anything, to do about any of the above is for the podling to decide.
>
>
> Mark
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message