+1 on keeping the volume on the list manageable. A project with a high volume list is difficult to contribute to if that project is not your main job, and we want to encourage a diversity of contributors.
A variation on what Henry is suggesting is to have jira send a message to the dev list only when a jira case is created. Subsequent updates go only to the issues list. But the initial email allows anyone interested to press "watch" on a case and receive all further updates for that case. Julian > On Mar 10, 2016, at 10:42 PM, Henry Saputra <[email protected]> wrote: > > Hi All, > > With Apache Eagle podling getting more active every day, it seemed like > JIRA updates and Github mirror updates start to become clutter to the dev > list. > > I think it is time to introduce new list, typically called issues@ as the > reservoir for the updates. > > We will still need to make JIRA create event to be delivered to dev@ for > bookeeping but updates could be redirected to issues@ > > This is one of the "good" problems to have =) > > Let me know what you guys think. > > Thanks, > > Henry
