On Tue, May 28, 2013 at 5:11 PM, Justin Mclean <jus...@classsoftware.com>wrote:
> Hi, > > I know I'm probably responsible for the majority of JIRA traffic. I'm not > opposed to having all JIRA emails go to a new list but there a few things > we should think about. > > Currently the JIRA messages are very easy to filter out so moving them to > another list is really no different to an email filter, it just happens to > be on for everyone. > > Apparently it is not so straightforward. Otherwise we wont have this issue now. > Do we want committers and developers to not see that new bugs are raised > or bugs fixed? Perhaps a solution is to have new bug requests and resolved > message still go to the dev list but all other messages (tagging etc) go to > a new list? > Which is why I suggested that committers/PMC members will be auto added to the new jira specific mailing list. > > What about having a once a day (or week) summary sent to the dev list so > at least people know what been going on and can comment or help out of > needed. > If that can be set up, I wont have objections. > > How do we handle the discussion of JIRA bugs? I think that probably needs > to be on the dev list (so the reply to address of the new JIRA mailing list > would need to be the dev list?) > Same way we discuss commits. All commit notifications goes to comm...@flex.apache.org. If someone wants to start a conversation, they just reply to the dev@flex.a.o list. > > Thanks, > Justin
