Re: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Jason van Zyl
Kenney Westerhof wrote: On Wed, 22 Feb 2006, Brett Porter wrote: I personally think a separate jira list allows for the most flexibility. The same for continuum builds, which sometimes really spam the dev list. I think the dev list should be exclusively used by human posters writing real email,

Re: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Dennis Lundberg
Arnaud HERITIER wrote: +1 for another list [EMAIL PROTECTED] +0 to keep the existing configuration -1 to receive the issues on commits@maven.apache.org Arnaud I agree with Arnaud. -- Dennis Lundberg On 2/22/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: +1 (if I am allowed to vote :) To

RE: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Brian E. Fox
+1 for a separate list for flexibility. -Original Message- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 7:51 AM To: Maven Developers List Subject: Re: sending JIRA mail to commits@maven.apache.org Agreed with Yann and John Cheers, Vincent 2006/2

Re: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Vincent Siveton
Agreed with Yann and John Cheers, Vincent 2006/2/22, Yann Le Du <[EMAIL PROTECTED]>: > +1 for a jira specific list > For consistency's sake :) A list for each topic. You choose the information > you need. > > +0 for subscribing to filters from JIRA > Why not, but we still need a way to get the i

Re: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Yann Le Du
+1 for a jira specific list For consistency's sake :) A list for each topic. You choose the information you need. +0 for subscribing to filters from JIRA Why not, but we still need a way to get the issues as soon as they arrive, and not only once a day. +0 for RSS from JIRA filters There again, w

Re: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Kenney Westerhof
On Wed, 22 Feb 2006, Brett Porter wrote: I personally think a separate jira list allows for the most flexibility. The same for continuum builds, which sometimes really spam the dev list. I think the dev list should be exclusively used by human posters writing real email, discussing development. Us

Re: sending JIRA mail to commits@maven.apache.org

2006-02-22 Thread Arnaud HERITIER
+1 for another list [EMAIL PROTECTED] +0 to keep the existing configuration -1 to receive the issues on commits@maven.apache.org Arnaud On 2/22/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: > > +1 (if I am allowed to vote :) > > To avoid having a full inbox, I use gmane.org: > It turns mailing

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Geoffrey De Smet
+1 (if I am allowed to vote :) To avoid having a full inbox, I use gmane.org: It turns mailing lists into newsgroups. So actually with this email, I am using the newsgroup gmane.comp.jakarta.turbine.maven.devel . I can't filter that, so it's very hard to follow the conversations. Having a dif

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Emmanuel Venisse
-0 for the same reason. Emmanuel John Casey a écrit : -0 I filter it all into a separate folder anyway, so I don't notice. I would tend to think that jira issues are much closer to the types of discussions which are meant to take place here...commits are more of the ground-level implementat

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Lukas Theussl
-1 Anyone subscribed to the dev list should be interested in the evolution and development of the project (otherwise he wouldn't be subscribed). JIRA is a big part of that, it really belongs here. -Lukas Brett Porter wrote: What do folks think of doing this to make the dev traffic a bit fr

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Brett Porter
That's been my main hesitation to this point, so its good to get this feedback. What do you think of other solutions: - subscribe to commits@ and filter out the actual commits - subscribe to filters from JIRA (so you get a daily mail of all the open or new issues in a particular project) - use RSS

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread John Casey
-0 I filter it all into a separate folder anyway, so I don't notice. I would tend to think that jira issues are much closer to the types of discussions which are meant to take place here...commits are more of the ground-level implementation details. I get it all anyway, so if you all have a

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Yann Le Du
> What do folks think of doing this to make the dev traffic a bit > friendlier to the people just reading the messages? > > - Brett -0 as a non-developer, for the same reasons as Mike. As an external user who wants to keep informed of evolutions, JIRA is as important to me as dev discussions. But

Re: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Jan Nielsen
Jolly good idea. -Jan Brett Porter <[EMAIL PROTECTED]> 02/21/2006 07:11 PM Please respond to "Maven Developers List" To Maven Developers List cc Subject sending JIRA mail to commits@maven.apache.org What do folks think of doing this to make the dev traffic a bit friendlier to the p

RE: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Mike Perham
-1 JIRA is rather important for me to see and I would assume that would be true of anyone on the dev list. I'm less concerned with individual commits. I would personally prefer it the way it is today. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, Februa

RE: sending JIRA mail to commits@maven.apache.org

2006-02-21 Thread Scott Ryan
I vote a big +1 Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 7:11 PM To: Maven Developers List Subject: sending JIRA mail t