incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Animesh Chaturvedi <>
Subject RE: [DISCUSS] Adjust JIRA to send out less mails (e.g. only about issue creation, status changes etc.)
Date Tue, 11 Dec 2012 23:10:41 GMT
Markmail archives and indexes all emails sent to cloudstack-dev.

Once the discussion is settled we can put a markmail search link for that discussion back
into Jira

-----Original Message-----
From: Alex Huang [] 
Sent: Friday, December 07, 2012 3:48 PM
Subject: RE: [DISCUSS] Adjust JIRA to send out less mails (e.g. only about issue creation,
status changes etc.)

I already have all my mail setup to filter JIRA emails to another folder so I'm actually okay
with JIRA "spamming".  However, I can certainly see people who don't have server side filtering
getting annoyed by emails spamming them on their devices for example.

I think to resolve David's concern, it just means developers must be conscientious about discussions
taking place on -dev.  We've been doing pretty good in terms of switching between -user and
-dev.  I don't see it as a problem for someone to says let's take this to the list on JIRA
itself.  Some will get drop but I doubt it's that big a deal.

I'm actually more concerned that discussions on the list are not captured in JIRA itself so
someone looking up a bug doesn't get the context of what has already been discussed about
the bug.  For that I propose that we tag all bug discussion emails.  It would be great if
someone who knows smtp to write a script to post to Jira on the appropriate tags.  Anyone
want to take that on?  Until we have that we have to make it a convention that searching for
a bug also means a search for the tag in the list to see if it's been discussed.


> -----Original Message-----
> From: David Nalley []
> Sent: Friday, December 07, 2012 3:02 PM
> To:
> Subject: Re: [DISCUSS] Adjust JIRA to send out less mails (e.g. only 
> about issue creation, status changes etc.)
> On Fri, Dec 7, 2012 at 5:46 PM, Rohit Yadav <> wrote:
> > I agree with Joe, JIRA should keep the same level of verbosity.
> > As Alex suggests, a good idea is to move them to a new mailing list 
> > (for
> commits, jira and review board updates etc.) and people who want to 
> receive those can join them. Can David or any asf-infra member help us 
> get a new mailing list for all of that?
> So while I am not inherently opposed to creation of a new list for 
> jira, review board, etc - I am very worried about the splintering 
> effect. Development discussions and decisions must happen on the -dev 
> list. Today some of those are happening in review board and jira, and 
> today those all circle back to the -dev list. IF Jira was only used as 
> a task list and seriously policed for that purpose I'd be more 
> amenable, but I just don't see it happening that way.
> (also as a side note - I have no privs on apmail - so can't help you 
> there - any officer can use the mlreq form though)
> --David

View raw message