Great, will create the mailing list and file ticket to INFRA to get this setup
- Henry On Fri, Feb 27, 2015 at 11:26 AM, Konstantin Boudnik <[email protected]> wrote: > Good idea +1 > > On Thu, Feb 26, 2015 at 09:57PM, Henry Saputra wrote: >> The idea is that the dev@ list would be the place where development >> happens. It means that by simply subscribing to dev@ list you should >> be able to find out if any new JIRA is filed. >> >> That is why I propose the initial JIRA creation still sent to dev@ list. >> >> - Henry >> >> On Thu, Feb 26, 2015 at 9:54 PM, Dmitriy Setrakyan >> <[email protected]> wrote: >> > I like the idea, but I would actually not send any JIRA emails to the dev >> > list, even when the Jira is created. I think it would be more consistent to >> > send them all to the "issues" list. >> > >> > D. >> > >> > On Fri, Feb 27, 2015 at 12:50 AM, Henry Saputra <[email protected]> >> > wrote: >> > >> >> HI All, >> >> >> >> To help dev@ list to be less nosiy, I would like to propose adding new >> >> mailing list called issues@ to contain all updates to JIRA issues. >> >> >> >> So when a JIRA is created, it will send email to both dev@ and issues@ >> >> but any subsequen updates will be sent to issues@ list. This include >> >> comments from Github mirror. >> >> >> >> Comments and suggestions are welcomed. >> >> >> >> - Henry >> >>
