Hi, I do not think that creating another list for issues solves the problem. JIRA mails can be easily filtered at the client side if you do not want to see them.
The main problem IMO with JIRA mails is that you can not see whether you should read a mail or not. The subject lines are just too generic. Having mails in commits@ is not much better. If the mails are just annoying we should get rid of them. Therefore, I would suggest to only send JIRA mails when an issue is created. If you want to keep track of things going on in JIRA, you should use the JIRA system directly. Best, - Fabian 2013/1/29 Sergio Fernández <[email protected]>: > Hi, > > yes, probably. Basically Apache projects follow three approaches to send the > issues notifications: > > a) to dev@ (as Marmotta or Jena do, for instance) > > b) to commits@ (Stanbol does this, I think) > > c) to third list, issues@ or whatever > > When we setup the project, we all agreed on Andy's suggestion (see [1]) to > send it here and get more attention of issues reporting. Personally I'll > disagree with the second options. But, due the traffic that Jira is > generated at dev@, maybe we can request the creation of issues@, making > mandatory its subscription to all committers. > > More opinions? > > Cheers, > > [1] http://markmail.org/message/rb6ow6vdvdlbv4vm > > > > On 29/01/13 11:17, Sebastian Schaffert wrote: >> >> Hi all, >> >> I think the amount of messages send by Jira to dev@... is getting a bit >> too >> much. I also think that the important mails disappear in the noise >> generated by Jira. Perhaps we can change the configuration in Jira so it >> only sends messages when an issue is created or commented, but not if >> someone starts progress or resolves an issue. >> >> What do you think? >> >> Greetings, >> >> Sebastian >> > > -- > Sergio Fernández -- Fabian http://twitter.com/fctwitt
