I like the idea of breaking PR discussions off, but if we're going to continue to copy PR comments onto Jira tickets it only makes sense if we have separate pr@ and issue@ lists. Also, we would have to stop copying them onto dev@ (which I would be fine with).
Ideally, I would like to see ticket _creation_ cc:ed onto dev@, so that any interested parties would be aware without having to set up notifications in Jira, but other ticket actions not cc:ed. I'm not sure if that's possible with our gear, but I'm sure INFRA can tell us. ajs6f > On May 30, 2019, at 10:42 AM, Andy Seaborne <a...@apache.org> wrote: > > The dev@ list can be dominated by github discussions. > > We have feeds from github PRs and JIRA. We could split the list in one list > per feed to leave the dev@ list for people. > > While you can do this with mail client rules, searching using the archives > isn't easy. > > Suggestion: > Add email lists for: > > pr@ -- github pull request discussions. > issues@ -- JIRA > > I'm not sure how clever we can be - for example, it would be nice for dev@ to > get an email for the submission of a pull request, then not the discussion, > but I don't think that is configurable. (It is all INFRa consifuration anyway > AFAIK). > > These names are the ones I have seen other projects use. > > Thoughts? > What have you seen work for other projects? > > Andy >
