You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Henry Saputra <he...@gmail.com> on 2015/02/27 06:50:28 UTC
[DISCUSS] Add new mailing list to send all JIRA updates
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
Re: [DISCUSS] Add new mailing list to send all JIRA updates
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Understood. I think we should do it.
D.
On Fri, Feb 27, 2015 at 12:57 AM, Henry Saputra <he...@gmail.com>
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
> <ds...@apache.org> 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 <henry.saputra@gmail.com
> >
> > 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
> >>
>
Re: [DISCUSS] Add new mailing list to send all JIRA updates
Posted by Konstantin Boudnik <co...@apache.org>.
To create the list you can just use
https://infra.apache.org/officers/mlreq
but for the custom routing, JIRA project admin would have to be involved.
Cos
On Mon, Mar 02, 2015 at 08:52PM, Henry Saputra wrote:
> 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 <co...@apache.org> 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
> >> <ds...@apache.org> 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 <he...@gmail.com>
> >> > 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
> >> >>
Re: [DISCUSS] Add new mailing list to send all JIRA updates
Posted by Henry Saputra <he...@gmail.com>.
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 <co...@apache.org> 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
>> <ds...@apache.org> 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 <he...@gmail.com>
>> > 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
>> >>
Re: [DISCUSS] Add new mailing list to send all JIRA updates
Posted by Konstantin Boudnik <co...@apache.org>.
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
> <ds...@apache.org> 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 <he...@gmail.com>
> > 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
> >>
Re: [DISCUSS] Add new mailing list to send all JIRA updates
Posted by Henry Saputra <he...@gmail.com>.
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
<ds...@apache.org> 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 <he...@gmail.com>
> 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
>>
Re: [DISCUSS] Add new mailing list to send all JIRA updates
Posted by Dmitriy Setrakyan <ds...@apache.org>.
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 <he...@gmail.com>
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
>