+1 to have JIRA create to @dev and updates to @issues. On Thu, 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 >
