Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
Locked
Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
 
Administrator
|
This post was updated on .
Hi all
Please discuss and vote, do you think what kind of JIRA issue events need send mails to dev@mailing list dev@carbondata.incubator.apache.org? Option1: None, all JIRA issue events don't need send any mails to dev@mailing list, users can directly go to apache jira to check issues' content. Option2:Issue Created and Issue Commented, the two JIRA issue events send mails to dev@mailing list Option3:Keep the current notification schema, the below events send mails to dev@mailing list. or any other option? In addition : Propose to move "pull request information from github" to issues@carbondata.incubator.apache.org also. For leveraging dev@carbondata.incubator.apache.org to focus on more solution/implementation/design discussion. ------------------------The below is current notification schema------------ EventsNotifications Issue Created - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Updated - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Assigned - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Resolved - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Closed - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Commented - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Comment Edited - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Comment Deleted - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Reopened - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Deleted - All Watchers - Current Assignee - Reporter - Single Email Address (dev@carbondata.incubator.apache.org) Issue Moved - Single Email Address (dev@carbondata.incubator.apache.org) Regards Liang |
|
|
option 2 is better
Regards jarray On 08/18/2016 15:57, Liang Big data wrote: Hi all Please discuss and vote, do you think what kind of JIRA issue events need send mails to [hidden email]? Option1: None, all JIRA issue events don't need send any mails to [hidden email], users can directly go to apache jira to check issues' content. Option2:Issue Created and Issue Commented, the two JIRA issue events send mails to [hidden email] Option3:Keep the current notification schema, the below events send mails to [hidden email]. or any other option? ------------------------The below is current notification schema------------ EventsNotifications Issue Created - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Updated - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Assigned - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Resolved - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Closed - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Commented - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Comment Edited - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Comment Deleted - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Reopened - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Deleted - All Watchers - Current Assignee - Reporter - Single Email Address ([hidden email]) Issue Moved - Single Email Address ([hidden email]) Regards Liang |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
+1 for option 2
On 18 August 2016 at 13:32, jarray <[hidden email]> wrote: > option 2 is better > > > > > Regards > jarray > On 08/18/2016 15:57, Liang Big data wrote: > Hi all > > Please discuss and vote, do you think what kind of JIRA issue events need > send mails to [hidden email]? > > Option1: None, all JIRA issue events don't need send any mails to > [hidden email], users can directly go to apache jira > to check issues' content. > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > mails to [hidden email] > > Option3:Keep the current notification schema, the below events send mails > to [hidden email]. > > or any other option? > > ------------------------The below is current notification > schema------------ > EventsNotifications > Issue Created > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Updated > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Assigned > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Resolved > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Closed > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Commented > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Edited > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Reopened > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Moved > > - Single Email Address ([hidden email]) > > > > Regards > Liang > -- Thanks & Regards, Ravi |
|
|
In reply to this post by Liang Chen
2
|
|
|
In reply to this post by Liang Chen
Option2, better add Issue closed event
|
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
In reply to this post by ravipesala
Any of this is fine with me.
Option 2.1: Issue Created and Issue Commented,+ issue resolved. + stop PR comment updating Jira comment. Option 4: Send them to another mailing list dev-notification On Thu, Aug 18, 2016 at 2:12 PM, Ravindra Pesala <[hidden email]> wrote: > +1 for option 2 > > On 18 August 2016 at 13:32, jarray <[hidden email]> wrote: > > > option 2 is better > > > > > > > > > > Regards > > jarray > > On 08/18/2016 15:57, Liang Big data wrote: > > Hi all > > > > Please discuss and vote, do you think what kind of JIRA issue events need > > send mails to [hidden email]? > > > > Option1: None, all JIRA issue events don't need send any mails to > > [hidden email], users can directly go to apache > jira > > to check issues' content. > > > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > > mails to [hidden email] > > > > Option3:Keep the current notification schema, the below events send mails > > to [hidden email]. > > > > or any other option? > > > > ------------------------The below is current notification > > schema------------ > > EventsNotifications > > Issue Created > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Updated > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Assigned > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Resolved > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Closed > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Commented > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Comment Edited > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Comment Deleted > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Reopened > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Deleted > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Moved > > > > - Single Email Address ([hidden email]) > > > > > > > > Regards > > Liang > > > > > > -- > Thanks & Regards, > Ravi > |
|
|
In reply to this post by Liang Chen
+1 for option 2
在 2016年08月18日 15:57, Liang Big data 写道: > Hi all > > Please discuss and vote, do you think what kind of JIRA issue events need > send mails to [hidden email]? > > Option1: None, all JIRA issue events don't need send any mails to > [hidden email], users can directly go to apache jira > to check issues' content. > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > mails to [hidden email] > > Option3:Keep the current notification schema, the below events send mails > to [hidden email]. > > or any other option? > > ------------------------The below is current notification schema------------ > EventsNotifications > Issue Created > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Updated > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Assigned > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Resolved > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Closed > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Commented > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Edited > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Reopened > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Moved > > - Single Email Address ([hidden email]) > > > > Regards > Liang > |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
In reply to this post by Liang Chen
How about modification of Option 2:
Issue Created, send mails to [hidden email] Issue Created and all other JIRA events send mails to new mailing list at [hidden email] - Henry On Thu, Aug 18, 2016 at 12:57 AM, Liang Big data <[hidden email]> wrote: > Hi all > > Please discuss and vote, do you think what kind of JIRA issue events need > send mails to [hidden email]? > > Option1: None, all JIRA issue events don't need send any mails to > [hidden email], users can directly go to apache jira > to check issues' content. > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > mails to [hidden email] > > Option3:Keep the current notification schema, the below events send mails > to [hidden email]. > > or any other option? > > ------------------------The below is current notification > schema------------ > EventsNotifications > Issue Created > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Updated > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Assigned > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Resolved > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Closed > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Commented > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Edited > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Reopened > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Moved > > - Single Email Address ([hidden email]) > > > > Regards > Liang > |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
Hi Henry,
This change sounds good to me. Make sense to have issues@. Lot of other projects have that as well. +1 for option 2, considering above changes Regards, Uma On Thu, Aug 18, 2016 at 11:43 AM, Henry Saputra <[hidden email]> wrote: > How about modification of Option 2: > > Issue Created, send mails to [hidden email] > > Issue Created and all other JIRA events send mails to new mailing list at > [hidden email] > > - Henry > > On Thu, Aug 18, 2016 at 12:57 AM, Liang Big data <[hidden email]> > wrote: > > > Hi all > > > > Please discuss and vote, do you think what kind of JIRA issue events need > > send mails to [hidden email]? > > > > Option1: None, all JIRA issue events don't need send any mails to > > [hidden email], users can directly go to apache > jira > > to check issues' content. > > > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > > mails to [hidden email] > > > > Option3:Keep the current notification schema, the below events send mails > > to [hidden email]. > > > > or any other option? > > > > ------------------------The below is current notification > > schema------------ > > EventsNotifications > > Issue Created > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Updated > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Assigned > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Resolved > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Closed > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Commented > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Comment Edited > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Comment Deleted > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Reopened > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Deleted > > > > - All Watchers > > - Current Assignee > > - Reporter > > - Single Email Address ([hidden email]) > > > > Issue Moved > > > > - Single Email Address ([hidden email]) > > > > > > > > Regards > > Liang > > > |
|
|
In reply to this post by Liang Chen
Option2：+1
在 2016/8/18 15:57, Liang Big data 写道: > Hi all > > Please discuss and vote, do you think what kind of JIRA issue events need > send mails to [hidden email]? > > Option1: None, all JIRA issue events don't need send any mails to > [hidden email], users can directly go to apache jira > to check issues' content. > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > mails to [hidden email] > > Option3:Keep the current notification schema, the below events send mails > to [hidden email]. > > or any other option? > > ------------------------The below is current notification schema------------ > EventsNotifications > Issue Created > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Updated > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Assigned > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Resolved > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Closed > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Commented > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Edited > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Reopened > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Moved > > - Single Email Address ([hidden email]) > > > > Regards > Liang > --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- |
|
|
In reply to this post by Liang Chen
option2
发自我的 iPhone > 在 2016年8月18日，下午3:57，Liang Big data <[hidden email]> 写道： > > Hi all > > Please discuss and vote, do you think what kind of JIRA issue events need > send mails to [hidden email]? > > Option1: None, all JIRA issue events don't need send any mails to > [hidden email], users can directly go to apache jira > to check issues' content. > > Option2:Issue Created and Issue Commented, the two JIRA issue events send > mails to [hidden email] > > Option3:Keep the current notification schema, the below events send mails > to [hidden email]. > > or any other option? > > ------------------------The below is current notification schema------------ > EventsNotifications > Issue Created > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Updated > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Assigned > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Resolved > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Closed > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Commented > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Edited > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Comment Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Reopened > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Deleted > > - All Watchers > - Current Assignee > - Reporter > - Single Email Address ([hidden email]) > > Issue Moved > > - Single Email Address ([hidden email]) > > > > Regards > Liang |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
Administrator
|
In reply to this post by Henry Saputra
Hi
I agree Henry's proposal. Issue Created, send mails to dev@mailing list Issue Created and all other JIRA events send mails to new mailing list at issues@mailing list. Regards Liang |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
+1 for option 2
On Aug 19, 2016 6:36 AM, "chenliang613" <[hidden email]> wrote: > Hi > > I agree Henry's proposal. > > Issue Created, send mails to dev@mailing list > Issue Created and all other JIRA events send mails to new mailing list at > issues@mailing list. > > > Regards > Liang > > > > -- > View this message in context: http://apache-carbondata- > mailing-list-archive.1130556.n5.nabble.com/Open-discussion- > and-Vote-What-kind-of-JIRA-issue-events-need-send-mail- > to-dev-carbondata-incubator-ag-tp321p332.html > Sent from the Apache CarbonData Mailing List archive mailing list archive > at Nabble.com. > |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
In reply to this post by Henry Saputra
Ok, if no objection I will ask INFRA to help makes the notification change
for option 2 plus new list issues@ Thanks! On Fri, Aug 19, 2016 at 7:57 PM, praveen adlakha <[hidden email]> wrote: > +1 for option 2. > > On Aug 20, 2016 8:22 AM, "Ravindra Pesala" <[hidden email]> wrote: > > > +1 for option 2 (Henry proposed solution). > > > > Thanks, > > Ravi. > > > > On Sat, 20 Aug 2016 7:54 am chenliang613, <[hidden email]> > wrote: > > > > > Agree for modified Option2 which be proposed by Henry. > > > We will implement it as per the solution. > > > > > > Thanks for all of you participated in discussion and vote. > > > > > > Regards > > > Liang > > > > > > > > > > > > -- > > > View this message in context: > > > http://apache-carbondata-mailing-list-archive.1130556. > > n5.nabble.com/Open-discussion-and-Vote-What-kind-of-JIRA- > > issue-events-need-send-mail-to-dev-carbondata-incubator- > ag-tp321p356.html > > > Sent from the Apache CarbonData Mailing List archive mailing list > archive > > > at Nabble.com. > > > > > > |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
|
Hi Henry,
I already requested the issues@ mailing list creation and Liang submitted a Jira to INFRA. Regards JB On 08/23/2016 07:27 PM, Henry Saputra wrote: > Ok, if no objection I will ask INFRA to help makes the notification change > for option 2 plus new list issues@ > > Thanks! > > On Fri, Aug 19, 2016 at 7:57 PM, praveen adlakha <[hidden email]> > wrote: > >> +1 for option 2. >> >> On Aug 20, 2016 8:22 AM, "Ravindra Pesala" <[hidden email]> wrote: >> >>> +1 for option 2 (Henry proposed solution). >>> >>> Thanks, >>> Ravi. >>> >>> On Sat, 20 Aug 2016 7:54 am chenliang613, <[hidden email]> >> wrote: >>> >>>> Agree for modified Option2 which be proposed by Henry. >>>> We will implement it as per the solution. >>>> >>>> Thanks for all of you participated in discussion and vote. >>>> >>>> Regards >>>> Liang >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://apache-carbondata-mailing-list-archive.1130556. >>> n5.nabble.com/Open-discussion-and-Vote-What-kind-of-JIRA- >>> issue-events-need-send-mail-to-dev-carbondata-incubator- >> ag-tp321p356.html >>>> Sent from the Apache CarbonData Mailing List archive mailing list >> archive >>>> at Nabble.com. >>>> >>> >> > -- Jean-Baptiste Onofré [hidden email] http://blog.nanthrax.net Talend - http://www.talend.com |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
Administrator
|
Yes. The submitted jira-INFRA is:
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-12475 Thanks for Henry's proposal. 2016-08-24 3:33 GMT+08:00 Jean-Baptiste Onofré <[hidden email]>: > Hi Henry, > > I already requested the issues@ mailing list creation and Liang submitted > a Jira to INFRA. > > Regards > JB > > On 08/23/2016 07:27 PM, Henry Saputra wrote: > >> Ok, if no objection I will ask INFRA to help makes the notification change >> for option 2 plus new list issues@ >> >> Thanks! >> >> On Fri, Aug 19, 2016 at 7:57 PM, praveen adlakha < >> [hidden email]> >> wrote: >> >> +1 for option 2. >>> >>> On Aug 20, 2016 8:22 AM, "Ravindra Pesala" <[hidden email]> >>> wrote: >>> >>> +1 for option 2 (Henry proposed solution). >>>> >>>> Thanks, >>>> Ravi. >>>> >>>> On Sat, 20 Aug 2016 7:54 am chenliang613, <[hidden email]> >>>> >>> wrote: >>> >>>> >>>> Agree for modified Option2 which be proposed by Henry. >>>>> We will implement it as per the solution. >>>>> >>>>> Thanks for all of you participated in discussion and vote. >>>>> >>>>> Regards >>>>> Liang >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://apache-carbondata-mailing-list-archive.1130556. >>>>> >>>> n5.nabble.com/Open-discussion-and-Vote-What-kind-of-JIRA- >>>> issue-events-need-send-mail-to-dev-carbondata-incubator- >>>> >>> ag-tp321p356.html >>> >>>> Sent from the Apache CarbonData Mailing List archive mailing list >>>>> >>>> archive >>> >>>> at Nabble.com. >>>>> >>>>> >>>> >>> >> > -- > Jean-Baptiste Onofré > [hidden email] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Regards Liang |
Re: Open discussion and Vote: What kind of JIRA issue events need send mail to dev@carbondata.incubator.apach
|
Administrator
|
Hi all
Propose to move "pull request information from github" to issues@carbondata.incubator.apache.org also. For leveraging dev@carbondata.incubator.apache.org to focus on more solution/implementation/design discussion. Please provide your opinion also. Regards Liang
|
«
Return to Apache CarbonData Dev Mailing List archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |