Finally I restricted to 4 the events which will send a notification to
the mailing list: creation, comment, closed and resolved.
Hope this will significantly reduce the unnecessary traffic, keeping
informed all people of the important things going on at the issue tracker.
Further details at INFRA-5807:
https://issues.apache.org/jira/browse/INFRA-5807
Cheers,
On 29/01/13 14:20, Andy Seaborne wrote:
On 29/01/13 10:46, Fabian Christ wrote:
2013/1/29 Fabian Christ <[email protected]>:
If you want to keep track of
things going on in JIRA, you should use the JIRA system directly.
Just wanted to add that this implies that JIRA is used to keep track
of things and to document actions. It is not meant to discuss things.
We should keep discussions on the mailing list and describe the
achieved consensus in a JIRA issue and implement that. The issue can
then be used as a reference for further discussions and first
documentation.
Ever project community has it's own character - as long as an interested
outside party can find out how the community operates, there are choices.
I see some JIRA discussions going on and if they don't go to dev@ they
may be missed by developers or interested observers who didn't know to
watch at the start. For example, a bug report may be from someone not
subscribed to dev@ and so a discussion on JIRA can be missed.
I hadn't seen the use of started/logged/... states on JIRA before. Maybe
the admin-ish messages can be stopped but keep comments, open and close.
Andy
--
Fabian
http://twitter.com/fctwitt
--
Sergio Fernández
