If someone is a very active contributor, he/she is most likely watching the commit list as well as the dev list. If someone is just subscribed to the dev list to watch the key discussions and occasionally gets involved, he/she would not want to see all the JIRA updates. This assumes that new discussions do not get triggered in JIRAs. They come to life on the mailing list and turn into a JIRA if they need to.
On 2/9/08, Simon Nash <[EMAIL PROTECTED]> wrote: > > ant elder wrote: > > On Feb 6, 2008 5:28 PM, Simon Nash <[EMAIL PROTECTED]> wrote: > > > > <snip> > > > >> One other consideration - sometimes it's appropriate to reply to a > >>> JIRA rather than updating the issue: if there are two lists, on has to > >>> decide - should the replies go to both or just dev? > >>> > >> In such a case I think the reply should just go to the dev list. All > >> discussions should be happening there, not on the commits list. > >> > > > > That can be done by having the JIRA emails configured with a replyto set > to > > the dev list, thats the same as the SVN update emails which are sent to > the > > commit list but replies to those emails go to the dev list. > > > > If it works like that would people feel more comfortable going ahead > with > > this change moving the JIRA emails to go to the commit list or is the > dev > > list still the preferred place? > > > > ...ant > > > I think the active committers could handle these on either list. It > would be useful to have input from those who are not active committers > and therefore (presumably) not following the commits list very closely. > I'd be happy to go with whatever these people prefer. > > Simon > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
